From 8a52256b7a23729c2d69abf9146fbcd5e970133e Mon Sep 17 00:00:00 2001
From: "john.xlm" <60260750+JFWooten4@users.noreply.github.com>
Date: Tue, 28 Apr 2026 14:21:39 -0400
Subject: [PATCH 1/6] delete Eng directory
---
i18n/en/code.json | 748 ------------
.../options.json | 14 -
.../current.json | 70 --
.../current.json | 342 ------
.../current.json | 1014 -----------------
i18n/en/docusaurus-theme-classic/footer.json | 98 --
i18n/en/docusaurus-theme-classic/navbar.json | 314 -----
7 files changed, 2600 deletions(-)
delete mode 100644 i18n/en/code.json
delete mode 100644 i18n/en/docusaurus-plugin-content-blog/options.json
delete mode 100644 i18n/en/docusaurus-plugin-content-docs-ap/current.json
delete mode 100644 i18n/en/docusaurus-plugin-content-docs-sdp/current.json
delete mode 100644 i18n/en/docusaurus-plugin-content-docs/current.json
delete mode 100644 i18n/en/docusaurus-theme-classic/footer.json
delete mode 100644 i18n/en/docusaurus-theme-classic/navbar.json
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"
- }
-}
From b0af610e72b1aa4c81a7da1e3f7ecea0000d2da0 Mon Sep 17 00:00:00 2001
From: "john.xlm" <60260750+JFWooten4@users.noreply.github.com>
Date: Tue, 28 Apr 2026 14:22:04 -0400
Subject: [PATCH 2/6] delete Esp directory
---
i18n/es/code.json | 748 --
.../2024-01-18.mdx | 33 -
.../2024-01-26.mdx | 34 -
.../2024-02-01.mdx | 28 -
.../2024-02-09.mdx | 21 -
.../2024-02-15.mdx | 44 -
.../2024-02-22.mdx | 20 -
.../2024-02-29.mdx | 20 -
.../2024-03-07.mdx | 21 -
.../2024-03-14.mdx | 24 -
.../2024-03-21.mdx | 22 -
.../2024-03-28.mdx | 21 -
.../2024-04-04.mdx | 33 -
.../2024-04-11.mdx | 22 -
.../2024-04-18.mdx | 20 -
.../2024-04-25.mdx | 25 -
.../2024-05-02.mdx | 23 -
.../2024-05-09.mdx | 19 -
.../2024-06-13.mdx | 25 -
.../2024-06-20.mdx | 20 -
.../2024-06-27.mdx | 22 -
.../2024-07-11.mdx | 18 -
.../2024-07-18.mdx | 21 -
.../2024-07-25.mdx | 23 -
.../2024-08-01.mdx | 18 -
.../2024-08-08.mdx | 15 -
.../2024-08-15.mdx | 24 -
.../2024-08-22.mdx | 31 -
.../2024-08-29.mdx | 27 -
.../2024-09-05.mdx | 30 -
.../2024-09-12.mdx | 28 -
.../2024-09-19.mdx | 26 -
.../2024-09-26.mdx | 22 -
.../2024-10-24.mdx | 25 -
.../2024-11-14.mdx | 27 -
.../2024-12-05.mdx | 12 -
.../2024-12-12.mdx | 12 -
.../2024-12-19.mdx | 12 -
.../2025-01-16.mdx | 12 -
.../2025-01-23.mdx | 28 -
.../2025-01-30.mdx | 28 -
.../2025-02-06.mdx | 32 -
.../2025-02-13.mdx | 36 -
.../2025-02-20.mdx | 34 -
.../2025-02-27.mdx | 36 -
.../2025-03-06.mdx | 20 -
.../2025-03-27.mdx | 28 -
.../2025-04-03.mdx | 20 -
.../2025-04-10.mdx | 18 -
.../2025-04-17.mdx | 20 -
.../2025-05-01.mdx | 30 -
.../2025-05-22.mdx | 15 -
.../2025-07-10.mdx | 19 -
.../2025-07-17.mdx | 19 -
.../2025-07-24.mdx | 23 -
.../2025-08-07.mdx | 19 -
.../2025-09-25.mdx | 23 -
.../2025-10-02.mdx | 17 -
.../2025-10-09.mdx | 36 -
.../2025-10-16.mdx | 17 -
.../2025-10-23.mdx | 17 -
.../2025-10-30.mdx | 17 -
.../2025-11-06.mdx | 21 -
.../authors.yml | 51 -
.../options.json | 14 -
.../current.json | 70 -
.../current/CONTRIBUTING.md | 251 -
.../current/README.mdx | 55 -
.../current/admin-guide/README.mdx | 10 -
.../current/admin-guide/_category_.json | 5 -
.../current/admin-guide/architecture.mdx | 71 -
.../admin-guide/assets-and-client-wallets.mdx | 117 -
.../component/observer/observer.mdx | 28 -
.../admin-guide/component/rpc/error.mdx | 16 -
.../admin-guide/component/rpc/request.mdx | 29 -
.../admin-guide/component/rpc/response.mdx | 33 -
.../current/admin-guide/component/rpc/rpc.mdx | 17 -
.../component/security/api_key.mdx | 14 -
.../admin-guide/component/security/jwt.mdx | 16 -
.../component/security/security.mdx | 11 -
.../admin-guide/custody-services/README.mdx | 10 -
.../custody-services/configuration.mdx | 130 -
.../custody-services/fireblocks/README.mdx | 10 -
.../fireblocks/configuration.mdx | 68 -
.../custody-services/fireblocks/example.mdx | 50 -
.../current/admin-guide/events/README.mdx | 10 -
.../current/admin-guide/events/delivery.mdx | 30 -
.../admin-guide/events/getting-started.mdx | 28 -
.../admin-guide/events/integration.mdx | 161 -
.../current/admin-guide/getting-started.mdx | 139 -
.../current/admin-guide/overview.mdx | 39 -
.../current/admin-guide/sep1/README.mdx | 66 -
.../current/admin-guide/sep10/README.mdx | 152 -
.../current/admin-guide/sep24/README.mdx | 10 -
.../admin-guide/sep24/configuration.mdx | 213 -
.../current/admin-guide/sep24/example.mdx | 438 -
.../current/admin-guide/sep24/faq.mdx | 39 -
.../admin-guide/sep24/getting-started.mdx | 34 -
.../current/admin-guide/sep24/integration.mdx | 1021 --
.../sep24/setting-up-production-server.mdx | 124 -
.../current/admin-guide/sep31/README.mdx | 10 -
.../admin-guide/sep31/configuration.mdx | 346 -
.../admin-guide/sep31/getting-started.mdx | 22 -
.../current/admin-guide/sep31/integration.mdx | 669 -
.../current/admin-guide/sep45/README.mdx | 90 -
.../current/admin-guide/sep6/README.mdx | 10 -
.../admin-guide/sep6/configuration.mdx | 267 -
.../admin-guide/sep6/getting-started.mdx | 34 -
.../current/admin-guide/sep6/integration.mdx | 991 --
.../current/api-reference/README.mdx | 10 -
.../current/api-reference/_category_.json | 3 -
.../api-reference/callbacks/README.mdx | 20 -
.../callbacks/del-customer.api.mdx | 80 -
.../callbacks/get-customer.api.mdx | 91 -
.../api-reference/callbacks/get-rates.api.mdx | 107 -
.../callbacks/post-event.api.mdx | 76 -
.../callbacks/put-customer.api.mdx | 85 -
.../api-reference/callbacks/versions.json | 12 -
.../current/api-reference/custody/README.mdx | 19 -
.../create-custody-transaction.api.mdx | 75 -
.../custody/generate-unique-address.api.mdx | 78 -
.../custody/send-payment.api.mdx | 75 -
.../api-reference/custody/send-refund.api.mdx | 75 -
.../api-reference/custody/versions.json | 12 -
.../current/api-reference/platform/README.mdx | 17 -
.../api-reference/platform/rpc/README.mdx | 10 -
.../platform/rpc/anchor-platform.openrpc.json | 10163 ----------------
.../platform/rpc/methods/README.mdx | 43 -
.../rpc/methods/do_stellar_payment.mdx | 13 -
.../rpc/methods/do_stellar_refund.mdx | 13 -
.../platform/rpc/methods/get_transaction.mdx | 11 -
.../platform/rpc/methods/get_transactions.mdx | 11 -
.../rpc/methods/notify_amounts_updated.mdx | 13 -
.../methods/notify_customer_info_updated.mdx | 15 -
.../notify_interactive_flow_completed.mdx | 15 -
.../notify_offchain_funds_available.mdx | 15 -
.../methods/notify_offchain_funds_pending.mdx | 15 -
.../notify_offchain_funds_received.mdx | 15 -
.../methods/notify_offchain_funds_sent.mdx | 15 -
.../methods/notify_onchain_funds_received.mdx | 15 -
.../rpc/methods/notify_onchain_funds_sent.mdx | 15 -
.../rpc/methods/notify_refund_pending.mdx | 13 -
.../rpc/methods/notify_refund_sent.mdx | 13 -
.../rpc/methods/notify_transaction_error.mdx | 15 -
.../methods/notify_transaction_expired.mdx | 15 -
.../methods/notify_transaction_on_hold.mdx | 15 -
.../methods/notify_transaction_recovery.mdx | 15 -
.../platform/rpc/methods/notify_trust_set.mdx | 11 -
.../rpc/methods/request_offchain_funds.mdx | 13 -
.../rpc/methods/request_onchain_funds.mdx | 13 -
.../platform/rpc/methods/request_trust.mdx | 11 -
.../api-reference/platform/rpc/overview.mdx | 16 -
.../platform/transactions/README.mdx | 19 -
.../transactions/get-transaction.api.mdx | 75 -
.../transactions/get-transactions.api.mdx | 75 -
.../platform/transactions/versions.json | 12 -
.../current/assets/SEP24-state-diagram.png | Bin 565132 -> 0 bytes
.../assets/anchor-platform-architecture-1.png | Bin 13560 -> 0 bytes
.../assets/anchor-platform-architecture-2.png | Bin 56436 -> 0 bytes
...chor-platform-sep24-demo-wallet-widget.png | Bin 633778 -> 0 bytes
.../anchor-platform-sep24-demo-wallet.png | Bin 447995 -> 0 bytes
...chor-platform-sep31-demo-wallet-widget.png | Bin 244757 -> 0 bytes
.../assets/sep24-deposit-flow-diagram.png | Bin 358498 -> 0 bytes
.../assets/sep24-withdrawal-flow-diagram.png | Bin 335686 -> 0 bytes
.../assets/sep31-transition-diagram.png | Bin 149171 -> 0 bytes
.../assets/sep6-deposit-flow-diagram.png | Bin 355832 -> 0 bytes
.../assets/sep6-withdrawal-flow-diagram.png | Bin 330509 -> 0 bytes
.../sequence_diagram_sep24_deposit_job.png | Bin 255794 -> 0 bytes
...sequence_diagram_sep24_deposit_webhook.png | Bin 267692 -> 0 bytes
.../sequence_diagram_sep24_withdrawal_job.png | Bin 244046 -> 0 bytes
...uence_diagram_sep24_withdrawal_webhook.png | Bin 214273 -> 0 bytes
.../sequence_diagram_sep31_receive_job.png | Bin 241196 -> 0 bytes
...sequence_diagram_sep31_receive_webhook.png | Bin 219754 -> 0 bytes
.../current/sep-guide/README.mdx | 10 -
.../current/sep-guide/_category_.json | 5 -
.../current/sep-guide/sep1/README.mdx | 200 -
.../current/sep-guide/sep10/README.mdx | 293 -
.../current/sep-guide/sep24/README.mdx | 10 -
.../current/sep-guide/sep24/configuration.mdx | 213 -
.../current/sep-guide/sep24/example.mdx | 438 -
.../current/sep-guide/sep24/faq.mdx | 39 -
.../sep-guide/sep24/getting-started.mdx | 34 -
.../current/sep-guide/sep24/integration.mdx | 929 --
.../sep24/setting-up-production-server.mdx | 124 -
.../current/sep-guide/sep31/README.mdx | 10 -
.../current/sep-guide/sep31/configuration.mdx | 346 -
.../sep-guide/sep31/getting-started.mdx | 22 -
.../current/sep-guide/sep31/integration.mdx | 620 -
.../current/sep-guide/sep45/README.mdx | 144 -
.../current/sep-guide/sep6/README.mdx | 10 -
.../current/sep-guide/sep6/configuration.mdx | 256 -
.../sep-guide/sep6/getting-started.mdx | 34 -
.../current/sep-guide/sep6/integration.mdx | 899 --
.../current/whats-new.mdx | 9 -
.../current.json | 342 -
.../current/README.mdx | 19 -
.../admin-guide/advanced-configration.mdx | 236 -
.../anchor-platform-integration-points.mdx | 44 -
.../current/admin-guide/cli-manual.mdx | 655 -
.../current/admin-guide/configuring-sdp.mdx | 241 -
.../current/admin-guide/deploy-the-sdp.mdx | 112 -
.../admin-guide/design-and-architecture.mdx | 78 -
.../current/admin-guide/getting-started.mdx | 110 -
.../making-your-wallet-sdp-ready.mdx | 178 -
.../current/admin-guide/monitoring.mdx | 58 -
.../current/admin-guide/overview.mdx | 20 -
.../admin-guide/secure-operation-manual.mdx | 44 -
.../current/admin-guide/security.mdx | 91 -
...ingle-tenant-to-multi-tenant-migration.mdx | 373 -
.../admin-guide/tenant-provisioning.mdx | 110 -
.../admin-guide/user-interface/README.mdx | 10 -
.../admin-guide/user-interface/analytics.mdx | 20 -
.../user-interface/circle-configuration.mdx | 24 -
.../user-interface/dashboard-home.mdx | 44 -
.../user-interface/disbursements.mdx | 26 -
.../admin-guide/user-interface/payments.mdx | 29 -
.../admin-guide/user-interface/receivers.mdx | 24 -
.../admin-guide/user-interface/wallets.mdx | 19 -
.../current/api-reference/_category_.json | 3 -
.../current/api-reference/admin.tag.mdx | 20 -
.../current/api-reference/api-keys.tag.mdx | 20 -
.../api-reference/authenticate-mfa.api.mdx | 74 -
.../api-reference/authentication.tag.mdx | 20 -
.../current/api-reference/balances.tag.mdx | 20 -
.../api-reference/bridge-integration.tag.mdx | 34 -
.../api-reference/create-api-key.api.mdx | 74 -
.../api-reference/create-asset.api.mdx | 74 -
.../create-direct-payment.api.mdx | 74 -
.../api-reference/create-disbursement.api.mdx | 74 -
.../api-reference/create-receiver.api.mdx | 74 -
.../api-reference/create-tenant.api.mdx | 74 -
.../current/api-reference/create-user.api.mdx | 74 -
.../api-reference/create-wallet.api.mdx | 74 -
.../api-reference/default-tenant.api.mdx | 77 -
.../delete-a-disbursement.api.mdx | 74 -
.../api-reference/delete-api-key.api.mdx | 74 -
.../api-reference/delete-asset.api.mdx | 74 -
.../api-reference/disbursements.tag.mdx | 20 -
...download-disbursement-instructions.api.mdx | 74 -
.../export-disbursements.api.mdx | 74 -
.../api-reference/export-payments-csv.api.mdx | 74 -
.../export-receivers-csv.api.mdx | 74 -
.../api-reference/forgot-password.api.mdx | 74 -
.../api-reference/get-all-assets.api.mdx | 66 -
.../api-reference/get-all-roles.api.mdx | 66 -
.../api-reference/get-all-tenants.api.mdx | 66 -
.../api-reference/get-all-users.api.mdx | 66 -
.../api-reference/get-all-wallets.api.mdx | 66 -
.../current/api-reference/get-api-key.api.mdx | 74 -
.../get-bridge-integration.api.mdx | 68 -
.../get-organization-circle-balances.api.mdx | 66 -
.../get-organization-info.api.mdx | 66 -
.../get-organization-logo.api.mdx | 66 -
.../current/api-reference/get-profile.api.mdx | 66 -
.../list-all-disbursement-receivers.api.mdx | 74 -
.../list-all-disbursements.api.mdx | 74 -
.../api-reference/list-all-payments.api.mdx | 74 -
.../api-reference/list-all-receivers.api.mdx | 74 -
.../api-reference/list-api-keys.api.mdx | 66 -
.../current/api-reference/log-in.api.mdx | 74 -
.../api-reference/organization.tag.mdx | 20 -
.../patch-organization-circle.api.mdx | 74 -
.../current/api-reference/payments.tag.mdx | 20 -
.../current/api-reference/profile.tag.mdx | 20 -
...ovide-signed-challenge-transaction.api.mdx | 74 -
.../current/api-reference/receivers.tag.mdx | 23 -
.../api-reference/refresh-token.api.mdx | 66 -
.../api-reference/registration.tag.mdx | 25 -
.../request-challenge-transaction.api.mdx | 74 -
.../request-registration-url.api.mdx | 69 -
.../api-reference/reset-password.api.mdx | 74 -
.../retrieve-a-disbursement.api.mdx | 74 -
.../api-reference/retrieve-a-payment.api.mdx | 74 -
.../api-reference/retrieve-a-receiver.api.mdx | 74 -
.../api-reference/retrieve-a-tenant.api.mdx | 74 -
.../retrieve-all-statistics.api.mdx | 66 -
.../retrieve-disbursement-statistics.api.mdx | 74 -
.../retrieve-stellar-info-file.api.mdx | 66 -
.../send-one-time-passcode.api.mdx | 74 -
.../current/api-reference/sidebar.ts | 450 -
.../soft-delete-a-tenant.api.mdx | 74 -
.../start-wallet-registration.api.mdx | 74 -
.../current/api-reference/statistics.tag.mdx | 20 -
.../update-a-disbursement-status.api.mdx | 74 -
.../api-reference/update-a-tenant.api.mdx | 74 -
.../api-reference/update-api-key.api.mdx | 74 -
.../update-bridge-integration.api.mdx | 77 -
.../update-organization-profile.api.mdx | 74 -
.../api-reference/update-receiver.api.mdx | 74 -
.../update-user-activation-status.api.mdx | 74 -
.../api-reference/update-user-profile.api.mdx | 74 -
.../api-reference/update-user-role.api.mdx | 74 -
.../api-reference/update-wallet.api.mdx | 74 -
.../upload-disbursement-instructions.api.mdx | 74 -
.../current/api-reference/users.tag.mdx | 20 -
.../verify-receiver-registration.api.mdx | 74 -
.../current.json | 1262 --
.../current/README.mdx | 36 -
.../current/build/README.mdx | 60 -
.../current/build/apps/README.mdx | 14 -
.../application-design-considerations.mdx | 109 -
.../current/build/apps/dapp-frontend.mdx | 561 -
.../example-application-tutorial/README.mdx | 11 -
.../_category_.json | 7 -
.../account-creation.mdx | 195 -
.../anchor-integration/README.mdx | 11 -
.../anchor-integration/_category_.json | 7 -
.../anchor-integration/sep1.mdx | 26 -
.../anchor-integration/sep10.mdx | 321 -
.../anchor-integration/sep24.mdx | 279 -
.../anchor-integration/sep6.mdx | 323 -
.../anchor-integration/setup.mdx | 46 -
.../confirmation-modal.mdx | 250 -
.../contacts-list.mdx | 150 -
.../manage-trust.mdx | 255 -
.../example-application-tutorial/overview.mdx | 270 -
.../path-payment.mdx | 290 -
.../example-application-tutorial/payment.mdx | 290 -
.../querying-data.mdx | 345 -
.../current/build/apps/guestbook/README.mdx | 10 -
.../current/build/apps/guestbook/bindings.mdx | 129 -
.../current/build/apps/guestbook/frontend.mdx | 601 -
.../current/build/apps/guestbook/overview.mdx | 124 -
.../apps/guestbook/passkeys-prerequisites.mdx | 95 -
.../build/apps/guestbook/setup-passkeys.mdx | 253 -
.../build/apps/guestbook/smart-contract.mdx | 381 -
.../current/build/apps/ingest-sdk/README.mdx | 11 -
.../build/apps/ingest-sdk/_category_.json | 7 -
.../ingest-sdk/ingestion-pipeline-code.mdx | 301 -
.../build/apps/ingest-sdk/overview.mdx | 91 -
.../current/build/apps/overview.mdx | 30 -
.../current/build/apps/smart-wallets.mdx | 146 -
.../current/build/apps/swift-payment-app.mdx | 62 -
.../current/build/apps/wallet/CONTRIBUTING.md | 95 -
.../current/build/apps/wallet/README.md | 90 -
.../current/build/apps/wallet/README.mdx | 11 -
.../current/build/apps/wallet/_category_.json | 7 -
.../wallet/component/dart/configClient.mdx | 21 -
.../apps/wallet/component/dart/install.mdx | 7 -
.../build/apps/wallet/component/header.mdx | 12 -
.../apps/wallet/component/kt/configClient.mdx | 42 -
.../apps/wallet/component/kt/globalSigner.mdx | 7 -
.../apps/wallet/component/kt/httpConfig.mdx | 8 -
.../apps/wallet/component/kt/install.mdx | 6 -
.../apps/wallet/component/kt/watcher.mdx | 25 -
.../wallet/component/swift/globalSigner.mdx | 8 -
.../apps/wallet/component/swift/install.mdx | 1 -
.../wallet/component/ts/allowHttpInfo.mdx | 11 -
.../apps/wallet/component/ts/configClient.mdx | 18 -
.../wallet/component/ts/createKeypairInfo.mdx | 11 -
.../apps/wallet/component/ts/globalSigner.mdx | 11 -
.../apps/wallet/component/ts/install.mdx | 3 -
.../current/build/apps/wallet/intro.mdx | 202 -
.../current/build/apps/wallet/overview.mdx | 16 -
.../current/build/apps/wallet/sep10.mdx | 255 -
.../current/build/apps/wallet/sep24.mdx | 966 --
.../current/build/apps/wallet/sep30.mdx | 523 -
.../current/build/apps/wallet/sep38.mdx | 280 -
.../current/build/apps/wallet/sep6.mdx | 596 -
.../current/build/apps/wallet/sep7.mdx | 275 -
.../current/build/apps/wallet/stellar.mdx | 1408 ---
.../current/build/guides/README.mdx | 8 -
.../current/build/guides/archival/README.mdx | 8 -
.../build/guides/archival/_category_.json | 3 -
.../create-restoration-footprint-js.mdx | 116 -
.../archival/extend-persistent-entry-js.mdx | 145 -
.../guides/archival/restore-contract-js.mdx | 76 -
.../build/guides/archival/restore-data-js.mdx | 102 -
.../guides/archival/test-ttl-extension.mdx | 172 -
.../current/build/guides/auth/README.mdx | 8 -
.../current/build/guides/auth/_category_.json | 3 -
.../guides/auth/check-auth-tutorials.mdx | 1483 ---
.../guides/auth/contract-authorization.mdx | 450 -
.../current/build/guides/basics/README.mdx | 8 -
.../build/guides/basics/_category_.json | 3 -
.../guides/basics/automate-reset-data.mdx | 373 -
.../guides/basics/classic-transition.mdx | 47 -
.../build/guides/basics/create-account.mdx | 297 -
.../basics/follow-received-payments.mdx | 267 -
.../basics/send-and-receive-payments.mdx | 1409 ---
.../build/guides/basics/verify-trustlines.mdx | 329 -
.../current/build/guides/cli/README.mdx | 10 -
.../current/build/guides/cli/_category_.json | 3 -
.../build/guides/cli/asset-management.mdx | 291 -
.../build/guides/cli/contract-lifecycle.mdx | 66 -
.../build/guides/cli/deploy-contract.mdx | 18 -
.../cli/deploy-stellar-asset-contract.mdx | 55 -
.../guides/cli/extend-contract-instance.mdx | 25 -
.../guides/cli/extend-contract-storage.mdx | 38 -
.../build/guides/cli/extend-contract-wasm.mdx | 36 -
.../build/guides/cli/install-deploy.mdx | 15 -
.../current/build/guides/cli/install-wasm.mdx | 21 -
.../build/guides/cli/payments-and-assets.mdx | 62 -
.../guides/cli/restore-contract-instance.mdx | 16 -
.../guides/cli/restore-contract-storage.mdx | 34 -
.../cli/tx-new-create-claimable-balance.mdx | 248 -
.../current/build/guides/cli/tx-new.mdx | 193 -
.../current/build/guides/cli/tx-op-add.mdx | 51 -
.../current/build/guides/cli/tx-sign.mdx | 76 -
.../build/guides/contract-accounts/README.mdx | 25 -
.../guides/contract-accounts/_category_.json | 3 -
.../contract-accounts/advanced-patterns.mdx | 49 -
.../guides/contract-accounts/examples.mdx | 47 -
.../contract-accounts/smart-wallets.mdx | 52 -
.../build/guides/conventions/README.mdx | 8 -
.../build/guides/conventions/_category_.json | 3 -
.../conventions/check-auth-tutorials.mdx | 1483 ---
.../guides/conventions/cross-contract.mdx | 130 -
.../guides/conventions/deploy-contract.mdx | 241 -
.../conventions/deploy-sac-with-code.mdx | 153 -
.../build/guides/conventions/error-enum.mdx | 41 -
.../guides/conventions/extending-wasm-ttl.mdx | 180 -
.../conventions/upgrading-contracts.mdx | 304 -
.../guides/conventions/wasm-metadata.mdx | 32 -
.../conventions/work-contractspec-js.mdx | 7 -
.../build/guides/conventions/workspace.mdx | 331 -
.../build/guides/conversions/README.mdx | 8 -
.../build/guides/conversions/_category_.json | 3 -
.../conversions/address-conversions.mdx | 125 -
.../guides/conversions/address-to-bytesn.mdx | 12 -
.../guides/conversions/address-to-id.mdx | 7 -
.../guides/conversions/bytes-conversions.mdx | 113 -
.../guides/conversions/id-to-address.mdx | 8 -
.../guides/conversions/scval-conversions.mdx | 67 -
.../guides/conversions/string-conversions.mdx | 110 -
.../current/build/guides/dapps/README.mdx | 8 -
.../build/guides/dapps/_category_.json | 3 -
.../current/build/guides/dapps/docker.mdx | 138 -
.../build/guides/dapps/frontend-guide.mdx | 844 --
.../build/guides/dapps/initialization.mdx | 201 -
.../current/build/guides/dapps/react.mdx | 140 -
.../dapps/soroban-contract-init-template.mdx | 295 -
.../build/guides/dapps/state-archival.mdx | 353 -
.../dapps/working-with-contract-specs.mdx | 1338 --
.../current/build/guides/events/README.mdx | 8 -
.../build/guides/events/_category_.json | 3 -
.../current/build/guides/events/consume.mdx | 210 -
.../current/build/guides/events/ingest.mdx | 318 -
.../current/build/guides/events/publish.mdx | 87 -
.../current/build/guides/fees/README.mdx | 8 -
.../current/build/guides/fees/_category_.json | 3 -
.../fees/analyzing-smart-contract-cost.mdx | 596 -
.../build/guides/fees/cost-analysis.mdx | 7 -
.../current/build/guides/freighter/README.mdx | 8 -
.../build/guides/freighter/_category_.json | 3 -
.../guides/freighter/connect-testnet.mdx | 13 -
.../freighter/enable-soroban-tokens.mdx | 15 -
.../freighter/integrate-freighter-react.mdx | 42 -
.../guides/freighter/prompt-to-sign-tx.mdx | 13 -
.../guides/freighter/send-token-payments.mdx | 17 -
.../guides/freighter/sign-auth-entries.mdx | 9 -
.../guides/freighter/sign-soroban-xdrs.mdx | 15 -
.../current/build/guides/rpc/README.mdx | 8 -
.../current/build/guides/rpc/_category_.json | 3 -
.../rpc/generate-ledger-keys-python.mdx | 31 -
.../guides/rpc/retrieve-contract-code-js.mdx | 126 -
.../rpc/retrieve-contract-code-python.mdx | 124 -
.../build/guides/rpc/self-deploy-rpc.mdx | 7 -
.../build/guides/rpc/use-public-rpc.mdx | 7 -
.../current/build/guides/storage/README.mdx | 8 -
.../build/guides/storage/_category_.json | 3 -
.../build/guides/storage/choose-type.mdx | 7 -
.../storage/choosing-the-right-storage.mdx | 223 -
.../build/guides/storage/use-instance.mdx | 32 -
.../build/guides/storage/use-persistent.mdx | 38 -
.../build/guides/storage/use-temporary.mdx | 24 -
.../current/build/guides/testing/README.mdx | 9 -
.../build/guides/testing/_category_.json | 3 -
.../build/guides/testing/code-coverage.mdx | 60 -
...differential-tests-with-test-snapshots.mdx | 67 -
.../guides/testing/differential-tests.mdx | 114 -
.../build/guides/testing/fork-testing.mdx | 83 -
.../current/build/guides/testing/fuzzing.mdx | 175 -
.../guides/testing/integration-tests.mdx | 72 -
.../testing/ledger-snapshot-testing.mdx | 283 -
.../current/build/guides/testing/mocking.mdx | 126 -
.../build/guides/testing/mutation-testing.mdx | 37 -
.../guides/testing/test-contract-auth.mdx | 60 -
.../guides/testing/test-contract-events.mdx | 55 -
.../build/guides/testing/unit-tests.mdx | 81 -
.../current/build/guides/tokens/README.mdx | 9 -
.../build/guides/tokens/_category_.json | 3 -
.../build/guides/tokens/custom-sac-admin.mdx | 157 -
.../build/guides/tokens/deploying-a-sac.mdx | 93 -
.../guides/tokens/stellar-asset-contract.mdx | 110 -
.../build/guides/transactions/README.mdx | 8 -
.../build/guides/transactions/_category_.json | 3 -
.../guides/transactions/channel-accounts.mdx | 75 -
.../transactions/claimable-balances.mdx | 702 --
.../build/guides/transactions/clawbacks.mdx | 887 --
.../guides/transactions/create-account.mdx | 716 --
.../transactions/fee-bump-transactions.mdx | 142 -
.../install-deploy-contract-with-code.mdx | 248 -
.../transactions/install-wasm-bytecode.mdx | 301 -
.../transactions/invoke-contract-tx-sdk.mdx | 449 -
.../guides/transactions/path-payments.mdx | 107 -
.../pooled-accounts-muxed-accounts-memos.mdx | 458 -
.../send-and-receive-c-accounts.mdx | 218 -
.../send-and-receive-payments.mdx | 1136 --
.../simulateTransaction-Deep-Dive.mdx | 412 -
.../transactions/sponsored-reserves.mdx | 596 -
.../submit-transaction-wait-js.mdx | 48 -
.../transactions/upload-wasm-bytecode.mdx | 392 -
.../current/build/security-docs/README.mdx | 11 -
.../securing-web-based-projects.mdx | 70 -
.../security-docs/threat-modeling/README.mdx | 11 -
.../threat-modeling/STRIDE-template.mdx | 70 -
.../pizza-restaurant-example.mdx | 73 -
.../threat-modeling-description.mdx | 20 -
.../threat-modeling-how-to.mdx | 69 -
.../current/build/smart-contracts/README.mdx | 14 -
.../build/smart-contracts/_category_.json | 3 -
.../example-contracts/README.mdx | 19 -
.../example-contracts/TEMPLATE.mdx | 183 -
.../example-contracts/alloc.mdx | 132 -
.../example-contracts/atomic-multi-swap.mdx | 33 -
.../example-contracts/atomic-swap.mdx | 265 -
.../example-contracts/auth.mdx | 494 -
.../example-contracts/bls-signature.mdx | 494 -
.../example-contracts/complex-account.mdx | 455 -
.../example-contracts/cross-contract-call.mdx | 330 -
.../example-contracts/custom-account.mdx | 455 -
.../example-contracts/custom-types.mdx | 313 -
.../example-contracts/deployer.mdx | 414 -
.../example-contracts/errors.mdx | 402 -
.../example-contracts/events.mdx | 319 -
.../example-contracts/fungible-token.mdx | 297 -
.../example-contracts/fuzzing.mdx | 783 --
.../example-contracts/liquidity-pool.mdx | 882 --
.../example-contracts/logging.mdx | 293 -
.../example-contracts/mint-lock.mdx | 30 -
.../example-contracts/non-fungible-token.mdx | 235 -
.../example-contracts/simple-account.mdx | 175 -
.../example-contracts/single-offer-sale.mdx | 31 -
.../example-contracts/storage.mdx | 262 -
.../example-contracts/timelock.mdx | 33 -
.../example-contracts/tokens.mdx | 963 --
.../upgradeable-contract.mdx | 20 -
.../example-contracts/workspace.mdx | 283 -
.../getting-started/README.mdx | 14 -
.../getting-started/_category_.json | 3 -
.../deploy-increment-contract.mdx | 137 -
.../getting-started/deploy-to-testnet.mdx | 158 -
.../getting-started/hello-world-frontend.mdx | 178 -
.../getting-started/hello-world.mdx | 347 -
.../smart-contracts/getting-started/setup.mdx | 291 -
.../getting-started/storing-data.mdx | 204 -
.../build/smart-contracts/overview.mdx | 130 -
.../current/data/CONTRIBUTING.md | 3 -
.../current/data/README.mdx | 44 -
.../current/data/READ_FIRST.md | 7 -
.../current/data/analytics/README.mdx | 16 -
.../analytics-providers.mdx | 28 -
.../current/data/analytics/hubble/README.mdx | 32 -
.../analytics/hubble/analyst-guide/README.mdx | 10 -
.../hubble/analyst-guide/_category_.json | 3 -
.../hubble/analyst-guide/connecting.mdx | 144 -
.../analyst-guide/creating-visualizations.mdx | 166 -
.../analyst-guide/history-vs-state-tables.mdx | 72 -
.../analyst-guide/optimizing-queries.mdx | 231 -
.../queries-for-horizon-like-data.mdx | 899 --
.../hubble/analyst-guide/viewing-metadata.mdx | 60 -
.../analytics/hubble/data-catalog/README.mdx | 10 -
.../hubble/data-catalog/_category_.json | 3 -
.../data-catalog/data-dictionary/README.mdx | 14 -
.../data-catalog/data-dictionary/accounts.mdx | 49 -
.../data-dictionary/bronze/README.mdx | 18 -
.../bronze/account-signers.mdx | 35 -
.../data-dictionary/bronze/accounts.mdx | 49 -
.../bronze/claimable-balances.mdx | 46 -
.../bronze/config-settings.mdx | 77 -
.../data-dictionary/bronze/contract-code.mdx | 44 -
.../data-dictionary/bronze/contract-data.mdx | 45 -
.../data-dictionary/bronze/evicted-keys.mdx | 27 -
.../data-dictionary/bronze/history-assets.mdx | 31 -
.../bronze/history-contract-events.mdx | 41 -
.../bronze/history-effects.mdx | 266 -
.../bronze/history-ledgers.mdx | 49 -
.../bronze/history-operations.mdx | 154 -
.../data-dictionary/bronze/history-trades.mdx | 50 -
.../bronze/history-transactions.mdx | 67 -
.../bronze/liquidity-pools.mdx | 46 -
.../data-dictionary/bronze/offers.mdx | 47 -
.../data-dictionary/bronze/restored-key.mdx | 31 -
.../data-dictionary/bronze/trustlines.mdx | 44 -
.../data-dictionary/bronze/ttl.mdx | 33 -
.../data-dictionary/claimable-balances.mdx | 46 -
.../data-dictionary/contract-code.mdx | 44 -
.../data-dictionary/contract-data.mdx | 45 -
.../enriched-history-operations.mdx | 103 -
.../data-dictionary/gold/README.mdx | 16 -
.../gold/asset-balances-daily-agg.mdx | 33 -
.../data-dictionary/gold/fee-stats-agg.mdx | 56 -
.../data-dictionary/gold/trade-agg.mdx | 72 -
.../data-dictionary/gold/tvl-agg.mdx | 27 -
.../data-dictionary/history-assets.mdx | 31 -
.../history-contract-events.mdx | 40 -
.../data-dictionary/history-effects.mdx | 266 -
.../data-dictionary/history-ledgers.mdx | 47 -
.../data-dictionary/history-operations.mdx | 154 -
.../data-dictionary/history-trades.mdx | 50 -
.../data-dictionary/history-transactions.mdx | 67 -
.../data-dictionary/liquidity-pools.mdx | 46 -
.../data-catalog/data-dictionary/offers.mdx | 47 -
.../data-dictionary/silver/README.mdx | 28 -
.../silver/account-signers-current.mdx | 22 -
.../silver/accounts-current.mdx | 22 -
.../silver/accounts-snapshot.mdx | 83 -
.../silver/claimable-balances-current.mdx | 22 -
.../silver/config-settings-current.mdx | 22 -
.../silver/contract-code-current.mdx | 22 -
.../silver/contract-data-current.mdx | 22 -
.../silver/contract-data-snapshot.mdx | 79 -
.../enriched-history-operations-soroban.mdx | 22 -
.../silver/enriched-history-operations.mdx | 103 -
.../silver/evicted-keys-snapshot.mdx | 75 -
.../silver/liquidity-pools-current.mdx | 22 -
.../silver/liquidity-pools-snapshot.mdx | 63 -
.../data-dictionary/silver/offers-current.mdx | 22 -
.../silver/token-transfers-raw.mdx | 43 -
.../silver/trustlines-current.mdx | 22 -
.../silver/trustlines-snapshot.mdx | 65 -
.../data-dictionary/silver/ttl-current.mdx | 22 -
.../data-dictionary/trustlines.mdx | 44 -
.../data-catalog/data-dictionary/ttl.mdx | 33 -
.../hubble/data-catalog/data-lineage.mdx | 7 -
.../data-catalog/data-model-diagram.mdx | 14 -
.../hubble/developer-guide/README.mdx | 11 -
.../developer-guide/backfill/JS-UDF.mdx | 158 -
.../developer-guide/backfill/README.mdx | 16 -
.../developer-guide/backfill/data-import.mdx | 53 -
.../connecting-to-bigquery/README.mdx | 144 -
.../developer-guide/data-curation/README.mdx | 10 -
.../data-curation/architecture.mdx | 22 -
.../data-curation/getting-started.mdx | 128 -
.../data-curation/overview.mdx | 15 -
.../scheduling-and-orchestration/README.mdx | 10 -
.../architecture.mdx | 18 -
.../getting-started.mdx | 87 -
.../scheduling-and-orchestration/overview.mdx | 15 -
.../source-system-ingestion/README.mdx | 10 -
.../source-system-ingestion/architecture.mdx | 25 -
.../getting-started.mdx | 123 -
.../source-system-ingestion/overview.mdx | 12 -
.../developer-guide/visualization/README.mdx | 10 -
.../visualization/getting-started.mdx | 41 -
.../visualization/overview.mdx | 6 -
.../current/data/apis/README.mdx | 36 -
.../current/data/apis/api-providers.mdx | 58 -
.../current/data/apis/horizon/README.mdx | 42 -
.../data/apis/horizon/admin-guide/README.mdx | 11 -
.../apis/horizon/admin-guide/configuring.mdx | 170 -
.../admin-guide/ingestion-filtering.mdx | 97 -
.../apis/horizon/admin-guide/ingestion.mdx | 95 -
.../apis/horizon/admin-guide/installing.mdx | 76 -
.../apis/horizon/admin-guide/monitoring.mdx | 116 -
.../apis/horizon/admin-guide/overview.mdx | 17 -
.../horizon/admin-guide/prerequisites.mdx | 60 -
.../data/apis/horizon/admin-guide/running.mdx | 121 -
.../data/apis/horizon/admin-guide/scaling.mdx | 57 -
.../apis/horizon/admin-guide/upgrading.mdx | 139 -
.../apis/horizon/api-reference/README.mdx | 11 -
.../horizon/api-reference/_category_.json | 3 -
.../api-reference/aggregations/README.mdx | 19 -
.../aggregations/fee-stats/README.mdx | 14 -
.../aggregations/fee-stats/object.mdx | 166 -
.../aggregations/order-books/README.mdx | 18 -
.../aggregations/order-books/object.mdx | 129 -
.../aggregations/paths/README.mdx | 19 -
.../aggregations/paths/object.mdx | 135 -
.../trade-aggregations/README.mdx | 14 -
.../trade-aggregations/object.mdx | 236 -
.../cb-retrieve-related-operations.api.mdx | 71 -
.../cb-retrieve-related-transactions.api.mdx | 71 -
.../horizon/api-reference/errors/README.mdx | 19 -
.../api-reference/errors/error-handling.mdx | 230 -
.../errors/http-status-codes/README.mdx | 25 -
.../horizon-specific/README.mdx | 20 -
.../horizon-specific/before-history.mdx | 21 -
.../horizon-specific/stale-history.mdx | 21 -
.../horizon-specific/timeout.mdx | 27 -
.../horizon-specific/transaction-failed.mdx | 34 -
.../transaction-malformed.mdx | 29 -
.../errors/http-status-codes/standard.mdx | 49 -
.../horizon/api-reference/errors/response.mdx | 62 -
.../errors/result-codes/README.mdx | 22 -
.../operation-specific/README.mdx | 32 -
.../operation-specific/account-merge.mdx | 34 -
.../operation-specific/allow-trust.mdx | 34 -
.../operation-specific/bump-sequence.mdx | 19 -
.../operation-specific/change-trust.mdx | 31 -
.../operation-specific/create-account.mdx | 31 -
.../create-passive-sell-offer.mdx | 52 -
.../operation-specific/manage-buy-offer.mdx | 52 -
.../operation-specific/manage-data.mdx | 28 -
.../operation-specific/manage-sell-offer.mdx | 52 -
.../path-payment-strict-receive.mdx | 55 -
.../path-payment-strict-send.mdx | 55 -
.../operation-specific/payment.mdx | 46 -
.../operation-specific/set-options.mdx | 43 -
.../errors/result-codes/operations.mdx | 53 -
.../errors/result-codes/transactions.mdx | 70 -
.../api-reference/get-all-offers.api.mdx | 71 -
.../api-reference/get-all-trades.api.mdx | 71 -
.../get-data-by-account-id.api.mdx | 71 -
.../get-effects-by-account-id.api.mdx | 71 -
.../get-offer-by-offer-id.api.mdx | 71 -
.../get-offers-by-account-id.api.mdx | 71 -
.../get-operations-by-account-id.api.mdx | 71 -
.../get-payments-by-account-id.api.mdx | 71 -
.../get-trades-by-account-id.api.mdx | 71 -
.../get-trades-by-offer-id.api.mdx | 71 -
.../get-transactions-by-account-id.api.mdx | 71 -
.../api-reference/list-all-accounts.api.mdx | 71 -
.../api-reference/list-all-assets.api.mdx | 71 -
.../list-all-claimable-balances.api.mdx | 71 -
.../api-reference/list-all-effects.api.mdx | 71 -
.../api-reference/list-all-ledgers.api.mdx | 71 -
.../api-reference/list-all-operations.api.mdx | 71 -
.../api-reference/list-all-payments.api.mdx | 71 -
.../list-all-transactions.api.mdx | 71 -
.../list-liquidity-pools.api.mdx | 71 -
.../list-strict-receive-payment-paths.api.mdx | 74 -
.../list-strict-send-payment-paths.api.mdx | 74 -
.../list-trade-aggregations.api.mdx | 78 -
.../lp-retrieve-related-operations.api.mdx | 71 -
.../lp-retrieve-related-transactions.api.mdx | 71 -
.../api-reference/resources/README.mdx | 25 -
.../api-reference/resources/_category_.json | 3 -
.../resources/accounts/README.mdx | 26 -
.../resources/accounts/object.mdx | 248 -
.../api-reference/resources/assets/README.mdx | 18 -
.../api-reference/resources/assets/object.mdx | 116 -
.../resources/claimablebalances/README.mdx | 19 -
.../resources/claimablebalances/object.mdx | 118 -
.../resources/effects/README.mdx | 14 -
.../api-reference/resources/effects/types.mdx | 240 -
.../resources/ledgers/README.mdx | 21 -
.../resources/ledgers/object.mdx | 112 -
.../resources/liquiditypools/README.mdx | 21 -
.../api-reference/resources/offers/README.mdx | 20 -
.../api-reference/resources/offers/object.mdx | 91 -
.../resources/operations/README.mdx | 19 -
.../resources/operations/object/README.mdx | 71 -
.../operations/object/account-merge.mdx | 58 -
.../operations/object/allow-trust.mdx | 74 -
.../begin-sponsoring-future-reserves.mdx | 52 -
.../operations/object/bump-sequence.mdx | 54 -
.../resources/operations/object/buy-offer.mdx | 97 -
.../operations/object/change-trust.mdx | 77 -
.../object/claim-claimable-balance.mdx | 56 -
.../operations/object/create-account.mdx | 62 -
.../object/create-claimable-balance.mdx | 113 -
.../object/end-sponsoring-future-reserves.mdx | 52 -
.../object/extend-footprint-ttl.mdx | 35 -
.../object/invoke-host-function.mdx | 95 -
.../object/liquidity-pool-deposit.mdx | 113 -
.../object/liquidity-pool-withdraw.mdx | 89 -
.../operations/object/manage-data.mdx | 58 -
.../operations/object/passive-sell-offer.mdx | 98 -
.../object/path-payment-strict-receive.mdx | 116 -
.../object/path-payment-strict-send.mdx | 116 -
.../operations/object/restore-footprint.mdx | 23 -
.../operations/object/revoke-sponsorship.mdx | 76 -
.../operations/object/sell-offer.mdx | 97 -
.../operations/object/set-options.mdx | 84 -
.../resources/payments/README.mdx | 14 -
.../resources/payments/object.mdx | 74 -
.../api-reference/resources/trades/README.mdx | 18 -
.../api-reference/resources/trades/object.mdx | 119 -
.../resources/transactions/README.mdx | 27 -
.../resources/transactions/object.mdx | 161 -
.../retrieve-a-claimable-balance.api.mdx | 71 -
.../api-reference/retrieve-a-ledger.api.mdx | 71 -
.../retrieve-a-ledgers-effects.api.mdx | 71 -
.../retrieve-a-ledgers-operations.api.mdx | 71 -
.../retrieve-a-ledgers-payments.api.mdx | 71 -
.../retrieve-a-ledgers-transactions.api.mdx | 71 -
.../retrieve-a-liquidity-pool.api.mdx | 71 -
.../retrieve-a-transaction.api.mdx | 71 -
.../retrieve-a-transactions-effects.api.mdx | 71 -
...retrieve-a-transactions-operations.api.mdx | 71 -
.../retrieve-a-transactions-payments.api.mdx | 71 -
.../api-reference/retrieve-an-account.api.mdx | 71 -
.../retrieve-an-operation.api.mdx | 71 -
.../retrieve-an-operations-effects.api.mdx | 71 -
.../retrieve-an-order-book.api.mdx | 74 -
.../api-reference/retrieve-fee-stats.api.mdx | 63 -
.../retrieve-related-effects.api.mdx | 71 -
.../retrieve-related-trades.api.mdx | 71 -
.../apis/horizon/api-reference/sidebar.ts | 318 -
.../api-reference/structure/README.mdx | 13 -
.../api-reference/structure/consistency.mdx | 6 -
.../structure/pagination/README.mdx | 271 -
.../structure/pagination/page-arguments.mdx | 269 -
.../api-reference/structure/rate-limiting.mdx | 12 -
.../structure/response-format.mdx | 211 -
.../api-reference/structure/streaming.mdx | 27 -
.../horizon/api-reference/structure/xdr.mdx | 49 -
.../submit-a-transaction.api.mdx | 71 -
.../submit-async-transaction.api.mdx | 71 -
.../current/data/apis/horizon/providers.mdx | 31 -
.../data/apis/migrate-from-horizon-to-rpc.mdx | 134 -
.../migrate-from-horizon-to-rpc.mdx | 133 -
.../current/data/apis/rpc/README.mdx | 44 -
.../data/apis/rpc/admin-guide/README.mdx | 11 -
.../data/apis/rpc/admin-guide/configuring.mdx | 264 -
.../rpc/admin-guide/data-lake-integration.mdx | 114 -
.../data/apis/rpc/admin-guide/development.mdx | 82 -
.../data/apis/rpc/admin-guide/installing.mdx | 47 -
.../data/apis/rpc/admin-guide/monitoring.mdx | 106 -
.../apis/rpc/admin-guide/prerequisites.mdx | 19 -
.../data/apis/rpc/admin-guide/running.mdx | 17 -
.../data/apis/rpc/api-reference/README.mdx | 11 -
.../apis/rpc/api-reference/_category_.json | 3 -
.../apis/rpc/api-reference/methods/README.mdx | 25 -
.../rpc/api-reference/methods/_category_.json | 3 -
.../rpc/api-reference/methods/getEvents.mdx | 21 -
.../rpc/api-reference/methods/getFeeStats.mdx | 19 -
.../rpc/api-reference/methods/getHealth.mdx | 19 -
.../api-reference/methods/getLatestLedger.mdx | 19 -
.../methods/getLedgerEntries.mdx | 468 -
.../rpc/api-reference/methods/getLedgers.mdx | 21 -
.../rpc/api-reference/methods/getNetwork.mdx | 19 -
.../api-reference/methods/getTransaction.mdx | 86 -
.../api-reference/methods/getTransactions.mdx | 21 -
.../api-reference/methods/getVersionInfo.mdx | 21 -
.../api-reference/methods/sendTransaction.mdx | 197 -
.../methods/simulateTransaction.mdx | 29 -
.../rpc/api-reference/structure/README.mdx | 13 -
.../api-reference/structure/_category_.json | 3 -
.../api-reference/structure/data-format.mdx | 67 -
.../rpc/api-reference/structure/json-rpc.mdx | 69 -
.../api-reference/structure/pagination.mdx | 26 -
.../current/data/apis/rpc/providers.mdx | 45 -
.../current/data/indexers/README.mdx | 114 -
.../data/indexers/build-your-own/README.mdx | 28 -
.../build-your-own/galexie/README.mdx | 37 -
.../galexie/admin_guide/README.mdx | 6 -
.../galexie/admin_guide/_category_.json | 3 -
.../galexie/admin_guide/configuring.mdx | 84 -
.../admin_guide/full-history-exporting.mdx | 166 -
.../galexie/admin_guide/installing.mdx | 23 -
.../galexie/admin_guide/monitoring.mdx | 52 -
.../galexie/admin_guide/prerequisites.mdx | 44 -
.../galexie/admin_guide/running.mdx | 223 -
.../galexie/admin_guide/setup.mdx | 110 -
.../galexie/examples/README.mdx | 7 -
.../galexie/examples/gcs-export.mdx | 143 -
.../build-your-own/galexie/providers.mdx | 19 -
.../build-your-own/ingest-sdk/README.mdx | 38 -
.../ingest-sdk/developer_guide/README.mdx | 9 -
.../developer_guide/architecture.mdx | 14 -
.../developer_guide/ledgerbackends/README.mdx | 34 -
.../ledgerbackends/bufferedstoragebackend.mdx | 166 -
.../ledgerbackends/captivecore.mdx | 71 -
.../ledgerbackends/rpcledgerbackend.mdx | 90 -
.../developer_guide/ledgerreaders.mdx | 12 -
.../developer_guide/prerequisites.mdx | 10 -
.../ingest-sdk/examples/README.mdx | 20 -
.../ingest-sdk/examples/changes.mdx | 209 -
.../examples/ledger_entry_statistics.mdx | 124 -
.../examples/transaction_statistics.mdx | 123 -
.../build-your-own/processors/README.mdx | 10 -
.../token-transfer-processor/README.mdx | 235 -
.../examples/README.mdx | 81 -
.../examples/event_stats.mdx | 82 -
.../examples/filter_events.mdx | 220 -
.../build-your-own/tutorials/README.mdx | 8 -
.../indexer-providers/indexer-providers.mdx | 34 -
.../current/data/oracles/README.mdx | 10 -
.../current/data/oracles/oracle-providers.mdx | 83 -
.../current/learn/encyclopedia/README.mdx | 10 -
.../network-configuration/README.mdx | 11 -
.../network-configuration/federation.mdx | 84 -
.../network-configuration/inflation.mdx | 13 -
.../network-configuration/ledger-headers.mdx | 114 -
.../network-passphrases.mdx | 17 -
.../learn/encyclopedia/sdex/README.mdx | 8 -
...uidity-on-stellar-sdex-liquidity-pools.mdx | 624 -
.../transactions-specialized/README.mdx | 8 -
.../channel-accounts.mdx | 76 -
.../claimable-balances.mdx | 436 -
.../transactions-specialized/clawbacks.mdx | 396 -
.../fee-bump-transactions.mdx | 129 -
.../transactions-specialized/memos.mdx | 24 -
.../path-payments.mdx | 33 -
.../pooled-accounts-muxed-accounts-memos.mdx | 348 -
.../sponsored-reserves.mdx | 550 -
.../current/learn/fundamentals/README.mdx | 14 -
.../current/learn/fundamentals/anchors.mdx | 63 -
.../contract-development/README.mdx | 8 -
.../contract-development/authorization.mdx | 169 -
.../contract-interactions/README.mdx | 10 -
.../contract-interactions/cross-contract.mdx | 25 -
.../contract-interactions/overview.mdx | 39 -
.../stellar-transaction.mdx | 629 -
.../contract-interactions/tests.mdx | 24 -
.../transaction-simulation.mdx | 215 -
.../contract-lifecycle.mdx | 70 -
.../environment-concepts.mdx | 68 -
.../errors-and-debugging/README.mdx | 10 -
.../errors-and-debugging/debugging-errors.mdx | 101 -
.../errors-and-debugging/debugging.mdx | 56 -
.../errors-and-debugging/errors.mdx | 46 -
.../contract-development/events.mdx | 235 -
.../contract-development/overview.mdx | 131 -
.../contract-development/rust-dialect.mdx | 85 -
.../contract-development/storage/README.mdx | 8 -
.../storage/persisting-data.mdx | 98 -
.../storage/state-archival.mdx | 387 -
.../transaction-lifecycle.mdx | 15 -
.../contract-development/types/README.mdx | 10 -
.../types/built-in-types.mdx | 97 -
.../types/custom-types.mdx | 125 -
.../types/fully-typed-contracts.mdx | 117 -
.../learn/fundamentals/data-format/README.mdx | 8 -
.../fundamentals/data-format/xdr-json.mdx | 40 -
.../learn/fundamentals/data-format/xdr.mdx | 223 -
.../fees-resource-limits-metering.mdx | 218 -
...uidity-on-stellar-sdex-liquidity-pools.mdx | 623 -
.../current/learn/fundamentals/lumens.mdx | 111 -
.../current/learn/fundamentals/networks.mdx | 128 -
.../stellar-consensus-protocol.mdx | 94 -
.../stellar-data-structures/README.mdx | 14 -
.../stellar-data-structures/accounts.mdx | 57 -
.../stellar-data-structures/assets.mdx | 118 -
.../stellar-data-structures/contracts.mdx | 10 -
.../stellar-data-structures/events.mdx | 296 -
.../stellar-data-structures/ledgers.mdx | 136 -
.../stellar-ecosystem-proposals.mdx | 182 -
.../learn/fundamentals/stellar-stack.mdx | 50 -
.../fundamentals/transactions/README.mdx | 12 -
.../transactions/list-of-operations.mdx | 773 --
.../operations-and-transactions.mdx | 184 -
.../transactions/signatures-multisig.mdx | 155 -
.../transactions/transaction-lifecycle.mdx | 56 -
.../current/learn/glossary.mdx | 400 -
.../current/learn/interactive/README.mdx | 10 -
.../current/learn/interactive/dapp-world.mdx | 8 -
.../current/learn/interactive/fca00c.mdx | 8 -
.../current/learn/interactive/quest.mdx | 10 -
.../current/learn/migrate/README.mdx | 10 -
.../current/learn/migrate/cosmos.mdx | 8 -
.../current/learn/migrate/evm/README.mdx | 10 -
.../evm/introduction-to-solidity-and-rust.mdx | 40 -
.../migrate/evm/smart-contract-deployment.mdx | 1293 --
.../solidity-and-rust-advanced-concepts.mdx | 907 --
.../migrate/evm/solidity-and-rust-basics.mdx | 642 -
.../evm/solidity-support-via-solang.mdx | 21 -
.../current/learn/migrate/near.mdx | 8 -
.../current/learn/migrate/solana.mdx | 8 -
.../current/networks/README.mdx | 140 -
.../current/networks/resource-limits-fees.mdx | 71 -
.../current/networks/software-versions.mdx | 1939 ---
.../current/platforms/README.mdx | 15 -
.../platforms/anchor-platform/CONTRIBUTING.md | 246 -
.../platforms/anchor-platform/README.mdx | 55 -
.../anchor-platform/admin-guide/README.mdx | 10 -
.../admin-guide/_category_.json | 5 -
.../admin-guide/architecture.mdx | 70 -
.../admin-guide/assets-and-client-wallets.mdx | 117 -
.../component/observer/observer.mdx | 28 -
.../admin-guide/component/rpc/error.mdx | 16 -
.../admin-guide/component/rpc/request.mdx | 29 -
.../admin-guide/component/rpc/response.mdx | 33 -
.../admin-guide/component/rpc/rpc.mdx | 17 -
.../component/security/api_key.mdx | 14 -
.../admin-guide/component/security/jwt.mdx | 16 -
.../component/security/security.mdx | 11 -
.../admin-guide/events/README.mdx | 10 -
.../admin-guide/events/delivery.mdx | 30 -
.../admin-guide/events/getting-started.mdx | 28 -
.../admin-guide/events/integration.mdx | 161 -
.../admin-guide/getting-started.mdx | 139 -
.../anchor-platform/api-reference/README.mdx | 10 -
.../api-reference/_category_.json | 3 -
.../api-reference/callbacks/README.mdx | 18 -
.../callbacks/del-customer.api.mdx | 80 -
.../callbacks/get-customer.api.mdx | 91 -
.../api-reference/callbacks/get-rates.api.mdx | 107 -
.../callbacks/post-event.api.mdx | 76 -
.../callbacks/put-customer.api.mdx | 85 -
.../api-reference/platform/README.mdx | 17 -
.../api-reference/platform/rpc/README.mdx | 10 -
.../platform/rpc/anchor-platform.openrpc.json | 10163 ----------------
.../platform/rpc/methods/README.mdx | 41 -
.../rpc/methods/do_stellar_payment.mdx | 13 -
.../rpc/methods/do_stellar_refund.mdx | 13 -
.../platform/rpc/methods/get_transaction.mdx | 11 -
.../platform/rpc/methods/get_transactions.mdx | 11 -
.../rpc/methods/notify_amounts_updated.mdx | 13 -
.../methods/notify_customer_info_updated.mdx | 15 -
.../notify_interactive_flow_completed.mdx | 15 -
.../notify_offchain_funds_available.mdx | 15 -
.../methods/notify_offchain_funds_pending.mdx | 15 -
.../notify_offchain_funds_received.mdx | 15 -
.../methods/notify_offchain_funds_sent.mdx | 15 -
.../methods/notify_onchain_funds_received.mdx | 15 -
.../rpc/methods/notify_onchain_funds_sent.mdx | 15 -
.../rpc/methods/notify_refund_pending.mdx | 13 -
.../rpc/methods/notify_refund_sent.mdx | 13 -
.../rpc/methods/notify_transaction_error.mdx | 15 -
.../methods/notify_transaction_expired.mdx | 15 -
.../methods/notify_transaction_on_hold.mdx | 15 -
.../methods/notify_transaction_recovery.mdx | 15 -
.../platform/rpc/methods/notify_trust_set.mdx | 11 -
.../rpc/methods/request_offchain_funds.mdx | 13 -
.../rpc/methods/request_onchain_funds.mdx | 13 -
.../platform/rpc/methods/request_trust.mdx | 11 -
.../api-reference/platform/rpc/overview.mdx | 16 -
.../platform/transactions/README.mdx | 17 -
.../transactions/get-transaction.api.mdx | 75 -
.../transactions/get-transactions.api.mdx | 75 -
.../anchor-platform/sep-guide/README.mdx | 10 -
.../anchor-platform/sep-guide/_category_.json | 5 -
.../anchor-platform/sep-guide/sep1/README.mdx | 198 -
.../sep-guide/sep10/README.mdx | 291 -
.../sep-guide/sep24/README.mdx | 10 -
.../sep-guide/sep24/configuration.mdx | 211 -
.../sep-guide/sep24/example.mdx | 438 -
.../anchor-platform/sep-guide/sep24/faq.mdx | 39 -
.../sep-guide/sep24/getting-started.mdx | 34 -
.../sep-guide/sep24/integration.mdx | 927 --
.../sep24/setting-up-production-server.mdx | 122 -
.../sep-guide/sep31/README.mdx | 10 -
.../sep-guide/sep31/configuration.mdx | 344 -
.../sep-guide/sep31/getting-started.mdx | 22 -
.../sep-guide/sep31/integration.mdx | 618 -
.../sep-guide/sep45/README.mdx | 142 -
.../anchor-platform/sep-guide/sep6/README.mdx | 10 -
.../sep-guide/sep6/configuration.mdx | 254 -
.../sep-guide/sep6/getting-started.mdx | 34 -
.../sep-guide/sep6/integration.mdx | 897 --
.../stellar-disbursement-platform/README.mdx | 19 -
.../admin-guide/advanced-configration.mdx | 236 -
.../admin-guide/cli-manual.mdx | 655 -
.../admin-guide/configuring-sdp.mdx | 241 -
.../admin-guide/deploy-the-sdp.mdx | 112 -
.../admin-guide/design-and-architecture.mdx | 78 -
.../admin-guide/getting-started.mdx | 110 -
.../making-your-wallet-sdp-ready.mdx | 176 -
.../admin-guide/monitoring.mdx | 58 -
.../admin-guide/overview.mdx | 20 -
.../admin-guide/security.mdx | 91 -
.../admin-guide/user-interface/README.mdx | 10 -
.../admin-guide/user-interface/analytics.mdx | 20 -
.../user-interface/circle-configuration.mdx | 24 -
.../user-interface/dashboard-home.mdx | 44 -
.../user-interface/disbursements.mdx | 26 -
.../admin-guide/user-interface/payments.mdx | 29 -
.../admin-guide/user-interface/receivers.mdx | 24 -
.../admin-guide/user-interface/wallets.mdx | 19 -
.../api-reference/_category_.json | 3 -
.../api-reference/admin.tag.mdx | 20 -
.../api-reference/api-keys.tag.mdx | 20 -
.../api-reference/authenticate-mfa.api.mdx | 74 -
.../api-reference/authentication.tag.mdx | 20 -
.../api-reference/balances.tag.mdx | 20 -
.../api-reference/bridge-integration.tag.mdx | 34 -
.../api-reference/create-api-key.api.mdx | 74 -
.../api-reference/create-asset.api.mdx | 74 -
.../create-direct-payment.api.mdx | 74 -
.../api-reference/create-disbursement.api.mdx | 74 -
.../api-reference/create-receiver.api.mdx | 74 -
.../api-reference/create-tenant.api.mdx | 74 -
.../api-reference/create-user.api.mdx | 74 -
.../api-reference/create-wallet.api.mdx | 74 -
.../api-reference/default-tenant.api.mdx | 77 -
.../delete-a-disbursement.api.mdx | 74 -
.../api-reference/delete-api-key.api.mdx | 74 -
.../api-reference/delete-asset.api.mdx | 74 -
.../api-reference/disbursements.tag.mdx | 20 -
...download-disbursement-instructions.api.mdx | 74 -
.../export-disbursements.api.mdx | 74 -
.../api-reference/export-payments-csv.api.mdx | 74 -
.../export-receivers-csv.api.mdx | 74 -
.../api-reference/forgot-password.api.mdx | 74 -
.../api-reference/get-all-assets.api.mdx | 66 -
.../api-reference/get-all-roles.api.mdx | 66 -
.../api-reference/get-all-tenants.api.mdx | 66 -
.../api-reference/get-all-users.api.mdx | 66 -
.../api-reference/get-all-wallets.api.mdx | 66 -
.../api-reference/get-api-key.api.mdx | 74 -
.../get-bridge-integration.api.mdx | 68 -
.../get-organization-circle-balances.api.mdx | 66 -
.../get-organization-info.api.mdx | 66 -
.../get-organization-logo.api.mdx | 66 -
.../api-reference/get-profile.api.mdx | 66 -
.../list-all-disbursement-receivers.api.mdx | 74 -
.../list-all-disbursements.api.mdx | 74 -
.../api-reference/list-all-payments.api.mdx | 74 -
.../api-reference/list-all-receivers.api.mdx | 74 -
.../api-reference/list-api-keys.api.mdx | 66 -
.../api-reference/log-in.api.mdx | 74 -
.../api-reference/organization.tag.mdx | 20 -
.../patch-organization-circle.api.mdx | 74 -
.../api-reference/payments.tag.mdx | 20 -
.../api-reference/profile.tag.mdx | 20 -
...ovide-signed-challenge-transaction.api.mdx | 74 -
.../api-reference/receivers.tag.mdx | 23 -
.../api-reference/refresh-token.api.mdx | 66 -
.../api-reference/registration.tag.mdx | 25 -
.../request-challenge-transaction.api.mdx | 74 -
.../request-registration-url.api.mdx | 69 -
.../api-reference/reset-password.api.mdx | 74 -
.../retrieve-a-disbursement.api.mdx | 74 -
.../api-reference/retrieve-a-payment.api.mdx | 74 -
.../api-reference/retrieve-a-receiver.api.mdx | 74 -
.../api-reference/retrieve-a-tenant.api.mdx | 74 -
.../retrieve-all-statistics.api.mdx | 66 -
.../retrieve-disbursement-statistics.api.mdx | 74 -
.../retrieve-stellar-info-file.api.mdx | 66 -
.../send-one-time-passcode.api.mdx | 74 -
.../api-reference/sidebar.ts | 435 -
.../soft-delete-a-tenant.api.mdx | 74 -
.../start-wallet-registration.api.mdx | 74 -
.../api-reference/statistics.tag.mdx | 20 -
.../update-a-disbursement-status.api.mdx | 74 -
.../api-reference/update-a-tenant.api.mdx | 74 -
.../api-reference/update-api-key.api.mdx | 74 -
.../update-bridge-integration.api.mdx | 77 -
.../update-organization-profile.api.mdx | 74 -
.../api-reference/update-receiver.api.mdx | 74 -
.../update-user-activation-status.api.mdx | 74 -
.../api-reference/update-user-profile.api.mdx | 74 -
.../api-reference/update-user-role.api.mdx | 74 -
.../api-reference/update-wallet.api.mdx | 74 -
.../upload-disbursement-instructions.api.mdx | 74 -
.../api-reference/users.tag.mdx | 20 -
.../verify-receiver-registration.api.mdx | 74 -
.../current/tokens/README.mdx | 93 -
.../current/tokens/anatomy-of-an-asset.mdx | 29 -
.../current/tokens/control-asset-access.mdx | 226 -
.../current/tokens/how-to-issue-an-asset.mdx | 759 --
.../current/tokens/publishing-asset-info.mdx | 369 -
.../current/tokens/quickstart.mdx | 112 -
.../current/tokens/stellar-asset-contract.mdx | 256 -
.../current/tokens/token-interface.mdx | 250 -
.../current/tools/README.mdx | 50 -
.../current/tools/cli/README.mdx | 13 -
.../current/tools/cli/_category_.json | 3 -
.../current/tools/cli/cookbook/README.mdx | 10 -
.../tools/cli/cookbook/_category_.json | 3 -
.../tools/cli/cookbook/asset-management.mdx | 291 -
.../cli/cookbook/contract-build-meta.mdx | 35 -
.../tools/cli/cookbook/contract-lifecycle.mdx | 66 -
.../tools/cli/cookbook/deploy-contract.mdx | 22 -
.../deploy-stellar-asset-contract.mdx | 55 -
.../cli/cookbook/extend-contract-instance.mdx | 25 -
.../cli/cookbook/extend-contract-storage.mdx | 38 -
.../cli/cookbook/extend-contract-wasm.mdx | 36 -
.../tools/cli/cookbook/install-deploy.mdx | 15 -
.../tools/cli/cookbook/install-wasm.mdx | 21 -
.../cli/cookbook/payments-and-assets.mdx | 62 -
.../cookbook/restore-contract-instance.mdx | 16 -
.../cli/cookbook/restore-contract-storage.mdx | 34 -
.../tools/cli/cookbook/stellar-keys.mdx | 124 -
.../tx-new-create-claimable-balance.mdx | 248 -
.../current/tools/cli/cookbook/tx-new.mdx | 189 -
.../current/tools/cli/cookbook/tx-op-add.mdx | 51 -
.../current/tools/cli/cookbook/tx-sign.mdx | 78 -
.../tools/cli/cookbook/upload-deploy.mdx | 15 -
.../tools/cli/cookbook/upload-wasm.mdx | 21 -
.../current/tools/cli/install-cli.mdx | 94 -
.../current/tools/cli/plugins-list.mdx | 37 -
.../current/tools/cli/plugins.mdx | 88 -
.../current/tools/cli/stellar-cli.mdx | 5233 --------
.../current/tools/developer-tools/IDEs.mdx | 7 -
.../current/tools/developer-tools/README.mdx | 14 -
.../tools/developer-tools/_category_.json | 3 -
.../current/tools/developer-tools/ai-bot.mdx | 27 -
.../developer-tools/analytics-platforms.mdx | 22 -
.../tools/developer-tools/anchor-tools.mdx | 20 -
.../tools/developer-tools/asset-tools.mdx | 12 -
.../tools/developer-tools/block-explorers.mdx | 22 -
.../developer-tools/jupyter-notebooks.mdx | 87 -
.../developer-tools/network-insights.mdx | 12 -
.../tools/developer-tools/network-status.mdx | 20 -
.../developer-tools/node-operator-tools.mdx | 12 -
.../openzeppelin-contracts.mdx | 93 -
.../developer-tools/openzepplin-contracts.mdx | 58 -
.../developer-tools/scaffold-stellar.mdx | 110 -
.../tools/developer-tools/security-tools.mdx | 26 -
.../current/tools/developer-tools/wallets.mdx | 60 -
.../current/tools/infra-tools/README.mdx | 10 -
.../current/tools/infra-tools/cross-chain.mdx | 33 -
.../current/tools/lab/README.mdx | 39 -
.../current/tools/lab/_category_.json | 3 -
.../current/tools/lab/account.mdx | 49 -
.../current/tools/lab/api-explorer/README.mdx | 14 -
.../lab/api-explorer/horizon-endpoint.mdx | 356 -
.../tools/lab/api-explorer/rpc-methods.mdx | 33 -
.../current/tools/lab/quickstart-with-lab.mdx | 33 -
.../current/tools/lab/saved/README.mdx | 12 -
.../current/tools/lab/saved/keypairs.mdx | 46 -
.../current/tools/lab/saved/requests.mdx | 44 -
.../current/tools/lab/saved/transactions.mdx | 22 -
.../tools/lab/smart-contracts/README.mdx | 29 -
.../lab/smart-contracts/contract-explorer.mdx | 126 -
.../smart-contracts/smart-contract-list.mdx | 12 -
.../upload-deploy-contract.mdx | 39 -
.../current/tools/lab/transactions.mdx | 39 -
.../current/tools/lab/view-xdr/README.mdx | 12 -
.../current/tools/lab/view-xdr/diff-xdr.mdx | 32 -
.../tools/lab/view-xdr/json-to-xdr.mdx | 33 -
.../tools/lab/view-xdr/xdr-to-json.mdx | 32 -
.../current/tools/openzeppelin-contracts.mdx | 119 -
.../current/tools/quickstart/README.mdx | 34 -
.../quickstart/advanced-usage/README.mdx | 16 -
.../quickstart/advanced-usage/_category_.json | 3 -
.../quickstart/advanced-usage/container.mdx | 21 -
.../advanced-usage/operation-modes.mdx | 44 -
.../tools/quickstart/advanced-usage/ports.mdx | 28 -
.../advanced-usage/run-command-examples.mdx | 104 -
.../advanced-usage/service-options.mdx | 28 -
.../current/tools/quickstart/cloud/README.mdx | 39 -
.../tools/quickstart/cloud/_category_.json | 3 -
.../tools/quickstart/cloud/digitalocean.mdx | 12 -
.../current/tools/quickstart/cloud/fly.io.mdx | 48 -
.../tools/quickstart/debugging/README.mdx | 16 -
.../quickstart/debugging/_category_.json | 3 -
.../debugging/diagnostic-events.mdx | 20 -
.../quickstart/debugging/viewing-logs.mdx | 20 -
.../current/tools/quickstart/explorer.mdx | 29 -
.../current/tools/quickstart/faucet.mdx | 17 -
.../quickstart/getting-started/README.mdx | 27 -
.../getting-started/_category_.json | 3 -
.../getting-started/connect-stellar-lab.mdx | 20 -
.../getting-started/deploy-smart-contract.mdx | 96 -
.../tools/quickstart/network-modes.mdx | 65 -
.../current/tools/ramps/README.mdx | 16 -
.../current/tools/ramps/moneygram.mdx | 9 -
.../current/tools/scaffold-stellar.mdx | 116 -
.../current/tools/sdks/README.mdx | 18 -
.../current/tools/sdks/_category_.json | 3 -
.../current/tools/sdks/build-your-own.mdx | 109 -
.../current/tools/sdks/client-sdks.mdx | 127 -
.../current/tools/sdks/contract-sdks.mdx | 80 -
.../current/validators/README.mdx | 70 -
.../current/validators/admin-guide/README.mdx | 12 -
.../validators/admin-guide/_category_.json | 3 -
.../validators/admin-guide/advanced.mdx | 48 -
.../validators/admin-guide/commands.mdx | 75 -
.../validators/admin-guide/configuring.mdx | 295 -
.../admin-guide/environment-preparation.mdx | 108 -
.../validators/admin-guide/installation.mdx | 106 -
.../validators/admin-guide/logging.mdx | 36 -
.../validators/admin-guide/maintenance.mdx | 40 -
.../validators/admin-guide/monitoring.mdx | 669 -
.../admin-guide/network-upgrades.mdx | 66 -
.../validators/admin-guide/prerequisites.mdx | 99 -
.../publishing-history-archives.mdx | 291 -
.../validators/admin-guide/running-node.mdx | 112 -
.../admin-guide/soroban-settings.mdx | 176 -
.../current/validators/tier-1-orgs.mdx | 86 -
.../docusaurus-plugin-content-pages/index.mdx | 36 -
.../platforms.mdx | 15 -
i18n/es/docusaurus-theme-classic/footer.json | 98 -
i18n/es/docusaurus-theme-classic/navbar.json | 314 -
1260 files changed, 154727 deletions(-)
delete mode 100644 i18n/es/code.json
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-01-18.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-01-26.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-02-01.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-02-09.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-02-15.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-02-22.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-02-29.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-03-07.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-03-14.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-03-21.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-03-28.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-04-04.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-04-11.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-04-18.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-04-25.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-05-02.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-05-09.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-06-13.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-06-20.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-06-27.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-07-11.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-07-18.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-07-25.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-08-01.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-08-08.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-08-15.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-08-22.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-08-29.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-09-05.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-09-12.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-09-19.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-09-26.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-10-24.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-11-14.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-12-05.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-12-12.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2024-12-19.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-01-16.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-01-23.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-01-30.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-02-06.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-02-13.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-02-20.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-02-27.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-03-06.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-03-27.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-04-03.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-04-10.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-04-17.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-05-01.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-05-22.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-07-10.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-07-17.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-07-24.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-08-07.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-09-25.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-10-02.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-10-09.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-10-16.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-10-23.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-10-30.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/2025-11-06.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/authors.yml
delete mode 100644 i18n/es/docusaurus-plugin-content-blog/options.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/CONTRIBUTING.md
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/architecture.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/assets-and-client-wallets.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/observer/observer.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/rpc/error.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/rpc/request.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/rpc/response.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/rpc/rpc.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/security/api_key.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/security/jwt.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/security/security.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/configuration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/fireblocks/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/fireblocks/configuration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/fireblocks/example.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/events/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/events/delivery.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/events/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/events/integration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep1/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep10/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/configuration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/example.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/faq.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/integration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/setting-up-production-server.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep31/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep31/configuration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep31/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep31/integration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep45/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep6/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep6/configuration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep6/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep6/integration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/del-customer.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/get-customer.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/get-rates.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/post-event.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/put-customer.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/versions.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/create-custody-transaction.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/generate-unique-address.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/send-payment.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/send-refund.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/versions.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/anchor-platform.openrpc.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/do_stellar_payment.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/do_stellar_refund.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/get_transaction.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/get_transactions.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_amounts_updated.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_customer_info_updated.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_interactive_flow_completed.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_offchain_funds_available.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_offchain_funds_pending.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_offchain_funds_received.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_offchain_funds_sent.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_onchain_funds_received.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_onchain_funds_sent.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_refund_pending.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_refund_sent.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_transaction_error.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_transaction_expired.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_transaction_on_hold.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_transaction_recovery.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_trust_set.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/request_offchain_funds.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/request_onchain_funds.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/request_trust.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/transactions/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/transactions/get-transaction.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/transactions/get-transactions.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/transactions/versions.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/assets/SEP24-state-diagram.png
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-architecture-1.png
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-architecture-2.png
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-sep24-demo-wallet-widget.png
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-sep24-demo-wallet.png
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-sep31-demo-wallet-widget.png
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep24-deposit-flow-diagram.png
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep24-withdrawal-flow-diagram.png
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep31-transition-diagram.png
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep6-deposit-flow-diagram.png
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep6-withdrawal-flow-diagram.png
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep24_deposit_job.png
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep24_deposit_webhook.png
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep24_withdrawal_job.png
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep24_withdrawal_webhook.png
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep31_receive_job.png
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep31_receive_webhook.png
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep1/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep10/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/configuration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/example.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/faq.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/integration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/setting-up-production-server.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep31/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep31/configuration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep31/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep31/integration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep45/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep6/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep6/configuration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep6/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep6/integration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-ap/current/whats-new.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/advanced-configration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/anchor-platform-integration-points.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/cli-manual.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/configuring-sdp.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/deploy-the-sdp.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/design-and-architecture.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/making-your-wallet-sdp-ready.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/monitoring.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/secure-operation-manual.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/security.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/single-tenant-to-multi-tenant-migration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/tenant-provisioning.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/analytics.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/circle-configuration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/dashboard-home.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/disbursements.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/payments.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/receivers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/wallets.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/admin.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/api-keys.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/authenticate-mfa.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/authentication.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/balances.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/bridge-integration.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-api-key.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-asset.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-direct-payment.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-disbursement.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-receiver.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-tenant.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-user.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-wallet.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/default-tenant.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/delete-a-disbursement.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/delete-api-key.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/delete-asset.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/disbursements.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/download-disbursement-instructions.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/export-disbursements.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/export-payments-csv.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/export-receivers-csv.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/forgot-password.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-assets.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-roles.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-tenants.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-users.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-wallets.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-api-key.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-bridge-integration.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-organization-circle-balances.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-organization-info.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-organization-logo.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-profile.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-all-disbursement-receivers.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-all-disbursements.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-all-payments.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-all-receivers.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-api-keys.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/log-in.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/organization.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/patch-organization-circle.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/payments.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/profile.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/provide-signed-challenge-transaction.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/receivers.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/refresh-token.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/registration.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/request-challenge-transaction.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/request-registration-url.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/reset-password.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-a-disbursement.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-a-payment.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-a-receiver.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-a-tenant.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-all-statistics.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-disbursement-statistics.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-stellar-info-file.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/send-one-time-passcode.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/sidebar.ts
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/soft-delete-a-tenant.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/start-wallet-registration.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/statistics.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-a-disbursement-status.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-a-tenant.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-api-key.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-bridge-integration.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-organization-profile.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-receiver.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-user-activation-status.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-user-profile.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-user-role.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-wallet.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/upload-disbursement-instructions.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/users.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/verify-receiver-registration.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/application-design-considerations.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/dapp-frontend.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/account-creation.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep1.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep10.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep24.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep6.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/setup.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/confirmation-modal.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/contacts-list.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/manage-trust.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/path-payment.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/payment.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/querying-data.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/bindings.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/frontend.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/passkeys-prerequisites.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/setup-passkeys.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/smart-contract.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/ingest-sdk/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/ingest-sdk/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/ingest-sdk/ingestion-pipeline-code.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/ingest-sdk/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/smart-wallets.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/swift-payment-app.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/CONTRIBUTING.md
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/README.md
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/dart/configClient.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/dart/install.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/header.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/configClient.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/globalSigner.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/httpConfig.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/install.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/watcher.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/swift/globalSigner.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/swift/install.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/allowHttpInfo.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/configClient.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/createKeypairInfo.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/globalSigner.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/install.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/intro.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep10.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep24.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep30.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep38.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep6.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep7.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/stellar.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/create-restoration-footprint-js.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/extend-persistent-entry-js.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/restore-contract-js.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/restore-data-js.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/test-ttl-extension.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/auth/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/auth/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/auth/check-auth-tutorials.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/auth/contract-authorization.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/automate-reset-data.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/classic-transition.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/create-account.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/follow-received-payments.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/send-and-receive-payments.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/verify-trustlines.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/asset-management.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/contract-lifecycle.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/deploy-contract.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/deploy-stellar-asset-contract.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/extend-contract-instance.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/extend-contract-storage.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/extend-contract-wasm.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/install-deploy.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/install-wasm.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/payments-and-assets.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/restore-contract-instance.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/restore-contract-storage.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/tx-new-create-claimable-balance.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/tx-new.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/tx-op-add.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/tx-sign.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/advanced-patterns.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/examples.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/smart-wallets.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/check-auth-tutorials.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/cross-contract.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/deploy-contract.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/deploy-sac-with-code.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/error-enum.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/extending-wasm-ttl.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/upgrading-contracts.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/wasm-metadata.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/work-contractspec-js.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/workspace.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/address-conversions.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/address-to-bytesn.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/address-to-id.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/bytes-conversions.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/id-to-address.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/scval-conversions.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/string-conversions.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/docker.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/frontend-guide.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/initialization.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/react.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/soroban-contract-init-template.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/state-archival.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/working-with-contract-specs.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/consume.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/ingest.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/publish.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/fees/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/fees/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/fees/analyzing-smart-contract-cost.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/fees/cost-analysis.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/connect-testnet.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/enable-soroban-tokens.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/integrate-freighter-react.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/prompt-to-sign-tx.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/send-token-payments.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/sign-auth-entries.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/sign-soroban-xdrs.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/generate-ledger-keys-python.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/retrieve-contract-code-js.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/retrieve-contract-code-python.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/self-deploy-rpc.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/use-public-rpc.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/choose-type.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/choosing-the-right-storage.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/use-instance.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/use-persistent.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/use-temporary.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/code-coverage.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/differential-tests-with-test-snapshots.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/differential-tests.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/fork-testing.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/fuzzing.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/integration-tests.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/ledger-snapshot-testing.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/mocking.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/mutation-testing.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/test-contract-auth.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/test-contract-events.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/unit-tests.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/custom-sac-admin.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/deploying-a-sac.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/stellar-asset-contract.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/channel-accounts.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/claimable-balances.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/clawbacks.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/create-account.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/fee-bump-transactions.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/install-deploy-contract-with-code.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/install-wasm-bytecode.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/invoke-contract-tx-sdk.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/path-payments.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/send-and-receive-c-accounts.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/send-and-receive-payments.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/simulateTransaction-Deep-Dive.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/sponsored-reserves.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/submit-transaction-wait-js.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/upload-wasm-bytecode.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/securing-web-based-projects.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/STRIDE-template.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/pizza-restaurant-example.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/threat-modeling-description.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/threat-modeling-how-to.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/TEMPLATE.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/alloc.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/atomic-multi-swap.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/atomic-swap.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/auth.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/bls-signature.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/complex-account.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/cross-contract-call.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/custom-account.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/custom-types.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/deployer.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/errors.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/events.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/fungible-token.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/fuzzing.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/liquidity-pool.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/logging.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/mint-lock.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/non-fungible-token.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/simple-account.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/single-offer-sale.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/storage.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/timelock.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/tokens.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/upgradeable-contract.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/workspace.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/deploy-increment-contract.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/deploy-to-testnet.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/hello-world-frontend.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/hello-world.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/setup.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/storing-data.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/CONTRIBUTING.md
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/READ_FIRST.md
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/analytics-providers/analytics-providers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/connecting.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/creating-visualizations.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/history-vs-state-tables.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/optimizing-queries.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/viewing-metadata.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/accounts.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/account-signers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/accounts.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/claimable-balances.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/config-settings.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-code.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-data.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/evicted-keys.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-assets.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-contract-events.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-effects.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-ledgers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-operations.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-trades.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-transactions.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/liquidity-pools.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/offers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/restored-key.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/trustlines.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/ttl.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/claimable-balances.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/contract-code.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/contract-data.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/enriched-history-operations.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/asset-balances-daily-agg.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/fee-stats-agg.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/trade-agg.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/tvl-agg.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-assets.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-contract-events.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-effects.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-ledgers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-operations.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-trades.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-transactions.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/liquidity-pools.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/offers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/account-signers-current.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-current.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-snapshot.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/claimable-balances-current.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-current.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-code-current.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-current.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-snapshot.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations-soroban.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/evicted-keys-snapshot.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-current.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-snapshot.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/offers-current.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/token-transfers-raw.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-current.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-snapshot.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/ttl-current.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/trustlines.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/ttl.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-lineage.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-model-diagram.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/backfill/JS-UDF.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/backfill/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/backfill/data-import.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/connecting-to-bigquery/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/data-curation/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/data-curation/architecture.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/data-curation/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/data-curation/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/scheduling-and-orchestration/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/scheduling-and-orchestration/architecture.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/scheduling-and-orchestration/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/scheduling-and-orchestration/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/source-system-ingestion/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/source-system-ingestion/architecture.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/source-system-ingestion/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/source-system-ingestion/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/visualization/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/visualization/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/visualization/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/api-providers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/configuring.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/ingestion-filtering.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/ingestion.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/installing.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/monitoring.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/prerequisites.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/running.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/scaling.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/upgrading.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/fee-stats/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/fee-stats/object.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/order-books/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/order-books/object.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/paths/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/paths/object.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/trade-aggregations/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/trade-aggregations/object.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/cb-retrieve-related-operations.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/cb-retrieve-related-transactions.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/error-handling.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/before-history.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/stale-history.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/timeout.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-malformed.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/standard.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/response.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/account-merge.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/allow-trust.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/bump-sequence.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/change-trust.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-account.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-passive-sell-offer.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-buy-offer.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-data.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-sell-offer.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-receive.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-send.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/payment.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/set-options.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operations.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/transactions.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-all-offers.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-all-trades.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-data-by-account-id.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-effects-by-account-id.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-offer-by-offer-id.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-offers-by-account-id.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-operations-by-account-id.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-payments-by-account-id.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-trades-by-account-id.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-trades-by-offer-id.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-transactions-by-account-id.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-accounts.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-assets.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-claimable-balances.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-effects.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-ledgers.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-operations.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-payments.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-transactions.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-liquidity-pools.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-strict-receive-payment-paths.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-strict-send-payment-paths.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-trade-aggregations.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/lp-retrieve-related-operations.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/lp-retrieve-related-transactions.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/accounts/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/accounts/object.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/assets/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/assets/object.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/claimablebalances/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/claimablebalances/object.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/effects/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/effects/types.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/ledgers/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/ledgers/object.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/liquiditypools/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/offers/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/offers/object.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/account-merge.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/allow-trust.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/begin-sponsoring-future-reserves.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/bump-sequence.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/buy-offer.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/change-trust.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/claim-claimable-balance.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/create-account.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/create-claimable-balance.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/end-sponsoring-future-reserves.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/extend-footprint-ttl.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/invoke-host-function.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-deposit.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-withdraw.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/manage-data.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/passive-sell-offer.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-receive.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-send.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/restore-footprint.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/revoke-sponsorship.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/sell-offer.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/set-options.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/payments/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/payments/object.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/trades/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/trades/object.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/transactions/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/transactions/object.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-claimable-balance.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledger.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-transaction.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-transactions-effects.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-transactions-operations.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-transactions-payments.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-an-account.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-an-operation.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-an-operations-effects.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-an-order-book.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-fee-stats.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-related-effects.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-related-trades.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/sidebar.ts
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/consistency.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/pagination/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/pagination/page-arguments.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/rate-limiting.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/response-format.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/streaming.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/xdr.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/submit-a-transaction.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/submit-async-transaction.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/providers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/migrate-from-horizon-to-rpc.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/migrate-from-horizon-to-rpc/migrate-from-horizon-to-rpc.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/configuring.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/data-lake-integration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/development.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/installing.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/monitoring.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/prerequisites.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/running.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getEvents.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getFeeStats.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getHealth.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getLatestLedger.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getLedgerEntries.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getLedgers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getNetwork.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getTransaction.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getTransactions.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getVersionInfo.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/sendTransaction.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/simulateTransaction.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/data-format.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/json-rpc.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/pagination.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/providers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/configuring.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/full-history-exporting.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/installing.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/monitoring.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/prerequisites.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/running.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/setup.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/examples/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/examples/gcs-export.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/providers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/architecture.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/bufferedstoragebackend.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/captivecore.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/rpcledgerbackend.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerreaders.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/prerequisites.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/examples/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/examples/changes.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/examples/ledger_entry_statistics.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/examples/transaction_statistics.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/token-transfer-processor/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/token-transfer-processor/examples/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/token-transfer-processor/examples/event_stats.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/token-transfer-processor/examples/filter_events.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/tutorials/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/indexers/indexer-providers/indexer-providers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/oracles/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/data/oracles/oracle-providers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/federation.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/inflation.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/ledger-headers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/network-passphrases.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/sdex/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/sdex/liquidity-on-stellar-sdex-liquidity-pools.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/channel-accounts.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/claimable-balances.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/clawbacks.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/fee-bump-transactions.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/memos.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/path-payments.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/pooled-accounts-muxed-accounts-memos.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/sponsored-reserves.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/anchors.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/authorization.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/cross-contract.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/tests.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-lifecycle.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/environment-concepts.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/errors-and-debugging/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/errors-and-debugging/debugging.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/errors-and-debugging/errors.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/events.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/rust-dialect.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/storage/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/storage/persisting-data.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/storage/state-archival.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/transaction-lifecycle.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/types/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/types/built-in-types.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/types/custom-types.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/types/fully-typed-contracts.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/data-format/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/data-format/xdr-json.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/data-format/xdr.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/fees-resource-limits-metering.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/lumens.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/networks.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-consensus-protocol.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/accounts.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/assets.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/contracts.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/events.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/ledgers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-ecosystem-proposals.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-stack.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/list-of-operations.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/operations-and-transactions.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/signatures-multisig.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/transaction-lifecycle.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/glossary.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/interactive/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/interactive/dapp-world.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/interactive/fca00c.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/interactive/quest.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/cosmos.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/introduction-to-solidity-and-rust.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/smart-contract-deployment.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/solidity-and-rust-advanced-concepts.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/solidity-and-rust-basics.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/solidity-support-via-solang.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/near.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/solana.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/networks/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/networks/resource-limits-fees.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/networks/software-versions.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/CONTRIBUTING.md
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/architecture.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/assets-and-client-wallets.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/observer/observer.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/rpc/error.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/rpc/request.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/rpc/response.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/rpc/rpc.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/security/api_key.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/security/jwt.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/security/security.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/events/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/events/delivery.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/events/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/events/integration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/del-customer.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/get-customer.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/get-rates.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/post-event.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/put-customer.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/anchor-platform.openrpc.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_payment.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_refund.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transaction.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transactions.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_amounts_updated.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_customer_info_updated.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_interactive_flow_completed.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_available.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_pending.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_received.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_sent.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_received.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_sent.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_pending.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_sent.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_error.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_expired.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_on_hold.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_recovery.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_trust_set.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/request_offchain_funds.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/request_onchain_funds.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/request_trust.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/transactions/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep1/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep10/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/configuration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/example.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/faq.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/integration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep31/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep31/configuration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep31/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep31/integration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep45/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep6/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep6/configuration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep6/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep6/integration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/advanced-configration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/cli-manual.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/configuring-sdp.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/deploy-the-sdp.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/design-and-architecture.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/getting-started.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/making-your-wallet-sdp-ready.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/monitoring.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/overview.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/security.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/analytics.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/circle-configuration.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/dashboard-home.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/disbursements.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/payments.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/receivers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/wallets.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/admin.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/api-keys.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/authentication.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/balances.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/bridge-integration.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-api-key.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-asset.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-disbursement.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-receiver.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-tenant.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-user.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-wallet.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/default-tenant.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/delete-api-key.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/delete-asset.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/disbursements.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/export-disbursements.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/forgot-password.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-assets.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-roles.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-tenants.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-users.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-api-key.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-organization-info.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-organization-logo.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-profile.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-all-payments.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-api-keys.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/log-in.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/organization.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/payments.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/profile.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/receivers.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/refresh-token.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/registration.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/request-registration-url.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/reset-password.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/sidebar.ts
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/statistics.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-api-key.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-organization-profile.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-receiver.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-user-profile.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-user-role.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-wallet.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/users.tag.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration.api.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tokens/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tokens/anatomy-of-an-asset.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tokens/control-asset-access.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tokens/how-to-issue-an-asset.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tokens/publishing-asset-info.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tokens/quickstart.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tokens/stellar-asset-contract.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tokens/token-interface.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/asset-management.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/contract-build-meta.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/contract-lifecycle.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/deploy-contract.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/deploy-stellar-asset-contract.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/extend-contract-instance.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/extend-contract-storage.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/extend-contract-wasm.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/install-deploy.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/install-wasm.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/payments-and-assets.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/restore-contract-instance.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/restore-contract-storage.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/stellar-keys.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/tx-new-create-claimable-balance.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/tx-new.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/tx-op-add.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/tx-sign.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/upload-deploy.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/upload-wasm.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/install-cli.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/plugins-list.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/plugins.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/cli/stellar-cli.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/IDEs.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/ai-bot.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/analytics-platforms.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/anchor-tools.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/asset-tools.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/block-explorers.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/jupyter-notebooks.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/network-insights.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/network-status.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/node-operator-tools.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/openzeppelin-contracts.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/openzepplin-contracts.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/scaffold-stellar.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/security-tools.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/wallets.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/infra-tools/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/infra-tools/cross-chain.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/account.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/api-explorer/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/api-explorer/horizon-endpoint.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/api-explorer/rpc-methods.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/quickstart-with-lab.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/saved/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/saved/keypairs.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/saved/requests.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/saved/transactions.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/smart-contracts/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/smart-contracts/contract-explorer.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/smart-contracts/smart-contract-list.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/smart-contracts/upload-deploy-contract.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/transactions.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/view-xdr/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/view-xdr/diff-xdr.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/view-xdr/json-to-xdr.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/lab/view-xdr/xdr-to-json.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/openzeppelin-contracts.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/container.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/operation-modes.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/ports.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/run-command-examples.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/service-options.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/cloud/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/cloud/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/cloud/digitalocean.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/cloud/fly.io.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/debugging/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/debugging/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/debugging/diagnostic-events.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/debugging/viewing-logs.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/explorer.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/faucet.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/getting-started/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/getting-started/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/getting-started/connect-stellar-lab.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/getting-started/deploy-smart-contract.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/network-modes.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/ramps/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/ramps/moneygram.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/scaffold-stellar.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/build-your-own.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/client-sdks.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/contract-sdks.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/validators/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/README.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/_category_.json
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/advanced.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/commands.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/configuring.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/environment-preparation.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/installation.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/logging.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/maintenance.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/monitoring.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/network-upgrades.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/prerequisites.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/publishing-history-archives.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/running-node.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/soroban-settings.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/validators/tier-1-orgs.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-pages/index.mdx
delete mode 100644 i18n/es/docusaurus-plugin-content-pages/platforms.mdx
delete mode 100644 i18n/es/docusaurus-theme-classic/footer.json
delete mode 100644 i18n/es/docusaurus-theme-classic/navbar.json
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
----
-
-
-
-[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
----
-
-
-
-[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
----
-
-
-
-[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
----
-
-
-
-[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
----
-
-
-
-[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
----
-
-
-
-[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
----
-
-
-
-[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
----
-
-
-
-[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
----
-
-
-
-[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
----
-
-
-
-[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
----
-
-
-
-[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):
-
-
-
-Parte 2 (video):
-
-
-
-[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
----
-
-
-
-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
----
-
-
-
-[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
----
-
-
-
-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
----
-
-
-
-[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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-[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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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";
-
-
-
-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";
-
-
-
-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";
-
-
-
-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";
-
-
-
-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";
-
-
-
-Parte 1
-
-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.
-
-
-
-Parte 2
-
-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 Discusión - https://github.com/stellar/stellar-protocol/discussions/1575
-
-CAP-0066 - https://github.com/stellar/stellar-protocol/blob/master/core/cap-0066.md 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";
-
-
-
-Parte 1
-
-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
-
-
-
-Parte 2
-
-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 Discusión - https://github.com/stellar/stellar-protocol/discussions/1610
-
-CAP-0065 - https://github.com/stellar/stellar-protocol/blob/master/core/cap-0065.md 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
-
-
-
-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
-
-
-
-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
-
-
-
-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
-
-
-
-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
-
-
-
-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
-
-
-
-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
-
-
-
-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
-
-
-
-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";
-
-
-
-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
-
-
-
-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
-
-
-
-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";
-
-
-
-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";
-
-
-
-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";
-
-
-
-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";
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-## 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)
-
-
-
-## 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
----
-
-
-
-## 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
----
-
-
-
-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
----
-
-
-
-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
----
-
-
-
-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
-
-¡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
-
-- [¡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.
-
-
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.
-
-
-
-#### 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.
-
-
-#### 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.
-
-
-
-```bash
-# dev.env
-PLATFORM_API_BASE_URL=http://platform-server:8085
-```
-
-
-
-:::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 @@
-
-
-| 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 |
-
-
-
-:::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:
-
-
-
-- 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
-
-
-
-:::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:
-
-
-
-- 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
-
-
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.
-
-
-
-```bash
-# call-json-rpc.sh
-#!/usr/bin/env bash
-
-curl localhost:8085 \
- -X POST \
- -H 'Content-Type: application/json' \
- --data "@$1"
-```
-
-
-
-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`:
-
-
-
-```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"
-```
-
-
-
-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`:
-
-
-
-```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"
-```
-
-
-
-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 `.
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.
-
-
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.
-
-
-
-```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
-```
-
-
-
-Configura el tipo de autenticación.
-
-
-
-```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
-```
-
-
-
-Si estableces el tipo de autenticación `api_key` o `jwt`, entonces necesitas agregar una variable de entorno.
-
-
-
-```bash
-# dev.env
-SECRET_CUSTODY_SERVER_AUTH_SECRET="Custody Server auth secret"
-```
-
-
-
-Inicia el Servidor de Custodia usando Gradle o Docker.
-
-
-
-```bash
-./gradlew service-runner:bootRun --args=--custody-server
-docker run stellar/anchor-platform:latest --custody-server
-```
-
-
-
-## 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.
-
-
-
-```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
-```
-
-
-
-:::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.
-
-
-
-```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
-```
-
-
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.
-
-
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.
-
-
-
-```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
-```
-
-
-
-Agrega las variables de entorno.
-
-
-
-```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"
-```
-
-
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 [](../../../assets/sequence_diagram_sep24_deposit_webhook.png)
-
-
-### 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 [](../../../assets/sequence_diagram_sep24_deposit_job.png)
-
-
-### Flujo de retiro SEP-24 con webhook:
-
-- do_stellar_payment
-- notify_onchain_funds_received
-- notify_offchain_funds_sent [](../../../assets/sequence_diagram_sep24_withdrawal_webhook.png)
-
-
-### Flujo de retiro SEP-24 con trabajo de conciliación:
-
-- request_onchain_funds
-- notify_onchain_funds_received
-- notify_offchain_funds_sent [](../../../assets/sequence_diagram_sep24_withdrawal_job.png)
-
-
-### Flujo de recepción SEP-31 con webhook:
-
-- notify_onchain_funds_received
-- notify_offchain_funds_sent [](../../../assets/sequence_diagram_sep31_receive_webhook.png)
-
-
-### Flujo de recepción SEP-31 con trabajo de conciliación:
-
-- notify_onchain_funds_received
-- notify_offchain_funds_sent [](../../../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.
-
-
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:
-
-
-
-```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
-```
-
-
-
-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.
-
-
-
-```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
-```
-
-
-
-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:
-
-
-
-```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
-```
-
-
-
-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:
-
-
-
-```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
-```
-
-
-
-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].
-
-
-
-```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"
-```
-
-
-
-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.
-
-
-
-```bash
-# dev.env
-SEP1_ENABLED=true
-SEP1_TOML_TYPE=file
-SEP1_TOML_VALUE=/home/dev.stellar.toml
-```
-
-
-
-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.
-
-
-
-```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"
-```
-
-
-
-`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.
-
-
-
-```bash
-# dev.env
-SEP10_CLIENT_ATTRIBUTION_REQUIRED=true
-```
-
-
-
-
-
-```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
-```
-
-
-
-`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.
-
-
-
-```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"
-```
-
-
-
-[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.
-
-
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.
-
-
-
-```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"
-```
-
-
-
-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.
-
-
-
-```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
-```
-
-
-
-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.
-
-
-
-```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
-```
-
-
-
-`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í.
-
-
-
-```
-├── dev.env
-├── docker-compose.yaml
-├── config
-│ ├── dev.assets.yaml
-│ ├── dev.stellar.toml
-```
-
-
-
-Tu entorno ahora debería verse así.
-
-
-
-```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"
-```
-
-
-
-Para probar esto, ve a la [Billetera Demostrativa Stellar][stellar-demo-wallet].
-
-[](../../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.
-
-[](../../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:
-
-
-
-```json
-{
- "jti": "e26cf292-814f-4918-9b40-b4f76a300f98",
- "sub": "GB244654NC6YPEFU3AY7L25COGES445P3Q63W6Q76JHR3UBJMLT2XBOB:1234567",
- "exp": 1516239022,
- "data": {
- "first_name": "John",
- "last_name": "Doe",
- "email": "johndoe@example.com"
- }
-}
-```
-
-
-
-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.
-
-
-
-```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"
- }
-}
-```
-
-
-
-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.
-
-
-
-```yaml
-# docker-compose.yaml
----
-business-server:
- build: .
- ports:
- - "8081:8081"
- env_file:
- - ./dev.env
- depends_on:
- - platform-server
-```
-
-
-
-Vamos a crear un contenedor Docker simple para nuestra aplicación.
-
-
-
-```docker
-FROM node:19
-
-WORKDIR /home
-COPY . .
-RUN npm install
-
-CMD ["node", "server.js"]
-```
-
-
-
-Ahora vamos a crear una aplicación NodeJS mínima.
-
-
-
-```bash
-yarn init -y
-yarn add express jsonwebtoken
-touch server.js
-```
-
-
-
-A continuación se presenta un ejemplo de un servidor backend autenticando a un usuario usando NodeJS.
-
-
-
-```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}`);
-});
-```
-
-
-
-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.
-
-
-
-```bash
-curl \
- -X POST \
- -H 'Content-Type: application/json' \
- -d '{"platformToken": ""}' \
- http://localhost:8081/session | jq
-```
-
-
-
-## 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.
-
-
-
-```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();
-}
-```
-
-
-
-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.
-
-
-
-```yaml
-# docker-compose.yml
----
-stellar-observer:
- image: stellar/anchor-platform:latest
- command: --stellar-observer
- env_file:
- - ./dev.env
- volumes:
- - ./config:/home
- depends_on:
- - db
-```
-
-
-
-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.
-
-
-
-```bash
-# dev.env
-PLATFORM_API_BASE_URL=http://platform-server:8085
-```
-
-
-
-Hagamos algunas adiciones al archivo `server.js` para que podamos consultar la Anchor Platform por nuestros pagos esperados.
-
-
-
-```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}`);
- }
- }
- }
-})()
-```
-
-
-
-## 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 `?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
-
-
-
-### Usando Clave API
-
-
-
-### Usando JWT
-
-
-
-## Realizando Solicitudes JSON-RPC
-
-
-
-### Solicitud JSON-RPC
-
-
-
-### Respuesta JSON-RPC
-
-
-
-### Códigos de Error
-
-
-
-## 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.
-
-[](../../assets/sep24-deposit-flow-diagram.png)
-
-:::tip
-
-Los estados en verde son obligatorios y definen la manera más corta.
-
-Los estados en amarillo son opcionales y pueden ser omitidos.
-
-Los estados en rojo 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`.
-
-
-
-```json
-// request-offchain-funds.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "request_offchain_funds",
- "params": {
- "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
- }
- }
- }
-]
-```
-
-
-
-- `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:
-
-
-
-```bash
-./call-json-rpc.sh request-offchain-funds.json
-```
-
-
-
-:::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`.
-
-
-
-```json
-// kyc-in-process.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_interactive_flow_completed",
- "params": {
- "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
- }
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh kyc-in-process.json
-```
-
-
-
-### Fondos Recibidos
-
-Si se recibieron fondos offchain, querrás proporcionar una información de transacción actualizada.
-
-
-
-```json
-// offchain-funds-received.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_offchain_funds_received",
- "params": {
- "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
- }
- }
- }
-]
-```
-
-
-
-- `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:
-
-
-
-```bash
-./call-json-rpc.sh offchain-funds-received.json
-```
-
-
-
-### 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.
-
-
-
-```json
-// offchain-funds-sent.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_offchain_funds_sent",
- "params": {
- "transaction_id": "",
- "message": "Offchain funds sent",
- "funds_received_at": "2023-07-04T12:34:56Z",
- "external_transaction_id": "7...9"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-
-
-### 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.
-
-
-
-```json
-// onchain-funds-sent.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_onchain_funds_sent",
- "params": {
- "transaction_id": "",
- "message": "Onchain funds sent",
- "stellar_transaction_id": "7...9"
- }
- }
-]
-```
-
-
-
-- `stellar_transaction_id` is the transaction id on Stellar network of the transfer
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh onchain-funds-sent.json
-```
-
-
-
-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:
-
-
-
-```json
-// do-stellar-payment.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "do_stellar_payment",
- "params": {
- "transaction_id": "",
- "message": "Custody payment started"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh do-stellar-payment.json
-```
-
-
-
-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:
-
-
-
-```json
-// request-trust.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "request_trust",
- "params": {
- "transaction_id": "",
- "message": "Asset trustine not configured"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh request-trust.json
-```
-
-
-
-:::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.
-
-
-
-```json
-// trust-set.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_trust_set",
- "params": {
- "transaction_id": "",
- "message": "Asset trustine set",
- "success": "true"
- }
- }
-]
-```
-
-
-
-- `success` flag que define si la trustline fue o no configurada por el usuario
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh trust-set.json
-```
-
-
-
-:::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.
-
-
-
-```json
-// refund-sent.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_refund_sent",
- "params": {
- "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"
- }
- }
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh refund-sent.json
-```
-
-
-
-:::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.
-
-
-
-```json
-// transaction-error.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_transaction_error",
- "params": {
- "transaction_id": "",
- "message": "Error occurred"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh transaction-error.json
-```
-
-
-
-:::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`:
-
-
-
-```json
-// transaction-expired.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_transaction_expired",
- "params": {
- "transaction_id": "",
- "message": "Transaction expired"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh transaction-expired.json
-```
-
-
-
-:::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.
-
-
-
-```json
-// transaction-hold.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_transaction_on_hold",
- "params": {
- "transaction_id": "",
- "message": "Transaction is on hold. Please contact customer support to resolve the hold."
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh transaction-hold.json
-```
-
-
-
-### 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:
-
-
-
-```json
-// transaction-recovery.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_transaction_recovery",
- "params": {
- "transaction_id": "",
- "message": "Transaction recovered"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh transaction-recovery.json
-```
-
-
-
-## 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.
-
-[](../../assets/sep24-withdrawal-flow-diagram.png)
-
-:::tip
-
-Los estados en verde son obligatorios y definen el camino más corto.
-
-Los estados en amarillo son opcionales y pueden ser omitidos.
-
-Los estados en rojo 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.
-
-
-
-```json
-// request-onchain-funds.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "request_onchain_funds",
- "params": {
- "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"
- }
- }
-]
-```
-
-
-
-- `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:
-
-
-
-```bash
-./call-json-rpc.sh request-onchain-funds.json
-```
-
-
-
-:::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`.
-
-
-
-```json
-// onchain-funds-received.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_onchain_funds_received",
- "params": {
- "transaction_id": "",
- "message": "Onchain funds received",
- "stellar_transaction_id": "7...9",
- "amount_in": {
- "amount": 10
- },
- "amount_out": {
- "amount": 9
- },
- "fee_details": {
- "total": 1
- }
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh onchain-funds-received.json
-```
-
-
-
-:::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`.
-
-
-
-```json
-// amounts-updated.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_amounts_updated",
- "params": {
- "transaction_id": "",
- "message": "Amounts updated",
- "amount_out": {
- "amount": 9
- },
- "fee_details": {
- "total": 1
- }
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh amounts-updated.json
-```
-
-
-
-:::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`.
-
-
-
-```json
-// offchain-funds-sent.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_offchain_funds_sent",
- "params": {
- "transaction_id": "",
- "message": "Offchain funds sent",
- "funds_sent_at": "2023-07-04T12:34:56Z",
- "external_transaction_id": "a...c"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-
-
-### 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.
-
-
-
-```json
-// offchain-funds-available.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_offchain_funds_available",
- "params": {
- "transaction_id": "",
- "message": "Offchain funds available",
- "external_transaction_id": "a...c"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh offchain-funds-available.json
-```
-
-
-
-### 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.
-
-
-
-```json
-// offchain-funds-pending.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_offchain_funds_pending",
- "params": {
- "transaction_id": "",
- "message": "Offchain funds pending",
- "external_transaction_id": "a...c"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh offchain-funds-pending.json
-```
-
-
-
-### 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.
-
-
-
-```json
-// do-stellar-refund.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "do_stellar_refund",
- "params": {
- "transaction_id": "",
- "message": "Do stellar refund",
- "refund": {
- "amount": {
- "amount": 9,
- "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
- },
- "amount_fee": {
- "amount": 1,
- "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
- }
- }
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh do-stellar-refund.json
-```
-
-
-
-:::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
-
-
-
-[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`):
-
-
-
-```toml
-# stellar.toml
-NETWORK_PASSPHRASE = "Public Global Stellar Network ; September 2015"
-```
-
-
-
-A continuación, cambia tu configuración de Anchor Platform en el archivo `production.env`:
-
-### Para la conexión al servidor Horizon:
-
-
-
-```bash
-# production.env STELLAR_NETWORK_NETWORK="Public"
-STELLAR_NETWORK_HORIZON_URL="https://horizon.stellar.org"
-```
-
-
-
-### Para la conexión al servidor RPC de Stellar:
-
-
-
-```bash
-# production.env STELLAR_NETWORK_NETWORK="Public"
-STELLAR_NETWORK_RPC_URL="https://mainnet.sorobanrpc.com"
-```
-
-
-
-## 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.
-
-
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.
-
-
-
-```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"
-```
-
-
-
-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`.
-
-
-
-```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
-```
-
-
-
-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.
-
-
-
-```bash
-# dev.env
-SEP31_ENABLED=true
-```
-
-
-
-Senders should now be able to discover, authenticate, and initiate transactions with your service! Ejecuta el siguiente comando para iniciar la Anchor Platform.
-
-
-
-```bash
-docker compose up
-```
-
-
-
-Verifica que tu API esté en vivo.
-
-
-
-```bash
-curl http://localhost:8080/sep31/info | jq
-```
-
-
-
-Deberías obtener lo siguiente.
-
-
-
-```json
-{
- "receive": {
- "USDC": {
- "enabled": true,
- "quotes_supported": true,
- "quotes_required": true,
- "min_amount": 0,
- "max_amount": 10000,
- "fields": {
- "transaction": {}
- }
- }
- }
-}
-```
-
-
-
-## 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.
-
-
-
-```toml
-# dev.stellar.toml
-KYC_SERVER = "http://localhost:8080/sep12"
-```
-
-
-
-Habilitemos también en nuestro entorno.
-
-
-
-```bash
-# dev.env
-SEP12_ENABLED=true
-```
-
-
-
-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.
-
-
-
-```yaml
-# dev.assets.yaml
-sep31:
- sep12:
- sender:
- types:
- sep31-sender:
- description: customers sending to recipients
- receiver:
- types:
- sep31-receiver:
- description: customers receiving from senders
-```
-
-
-
-Pingueemos nuevamente el endpoint de información para verificar. Después de `docker compose up`, ejecuta el siguiente comando:
-
-
-
-```bash
-curl http://localhost:8080/sep31/info | jq
-```
-
-
-
-Deberías obtener lo siguiente:
-
-
-
-```json
-{
- "receive": {
- "USDC": {
- "enabled": true,
- "quotes_supported": true,
- "quotes_required": true,
- "min_amount": 0,
- "max_amount": 10000,
- "fields": {
- "transaction": {}
- }
- }
- }
-}
-```
-
-
-
-## 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.
-
-
-
-```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"
-```
-
-
-
-Habilitemos también en nuestro entorno.
-
-
-
-```bash
-# dev.env
-SEP38_ENABLED=true
-```
-
-
-
-También necesitamos habilitar el uso de USDC en esta API, así como agregar un activo off-chain con el cual se pueda intercambiar.
-
-
-
-```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.
-```
-
-
-
-¡Probemos que tu API de RFQ está en vivo! Después de `docker compose up`:
-
-
-
-```bash
-curl http://localhost:8080/sep38/info | jq
-```
-
-
-
-Deberías obtener lo siguiente:
-
-
-
-```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."
- }
- ]
- }
- ]
-}
-```
-
-
-
-## 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.
-
-
-
-```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=
-```
-
-
-
-`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.
-
-
-
-```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
-```
-
-
-
-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:
-
-
-
-```json
-{
- "account": "GDJUOFZGW5WYBK4GIETCSSM6MTTIJ4SUMCQITPTLUWMQ6B4UIX2IEX47",
- "memo": "780284017",
- "type": "sep31-sender",
- "first_name": "John",
- "last_name": "Doe",
- "email": "johndoe@example.com"
-}
-```
-
-
-
-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.
-
-
-
-```json
-{
- "id": "fb5ddc93-1d5d-490d-ba5f-2c361cea41f7"
-}
-```
-
-
-
-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:
-
-
-
-```
-/customer?account=GDJUOFZGW5WYBK4GIETCSSM6MTTIJ4SUMCQITPTLUWMQ6B4UIX2IEX47&memo=780284017&type=sep31-sender
-```
-
-
-
-O, la organización remitente podría usar el identificador que devolviste cuando registraron originalmente al cliente.
-
-
-
-```
-/customer?id=fb5ddc93-1d5d-490d-ba5f-2c361cea41f7&type=sep31-sender
-```
-
-
-
-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.
-
-[](../../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.
-
-
-
-```yaml
-services:
- ...
- observer:
- image: stellar/anchor-platform:latest
- command: --stellar-observer
- env_file:
- - ./dev.env
- volumes:
- - ./config:/home
-```
-
-
-
-### 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:
-
-
-
-```bash
-curl http://localhost:8080/transactions?sep=31&order_by=transfer_received_at&order=desc
-```
-
-
-
-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.
-
-[](../../assets/sep31-transition-diagram.png)
-
-:::tip
-
-Los estados en verde son obligatorios y definen el flujo más corto.
-
-Los estados en amarillo son opcionales y pueden omitirse.
-
-Los estados en rojo 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:
-
-
-
-```json
-// request-onchain-funds.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "request_onchain_funds",
- "params": {
- "transaction_id": "",
- "message": "Request onchain funds",
- "destination_account": "GD...G",
- "memo": "12345",
- "memo_type": "id"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh request-onchain-funds.json
-```
-
-
-
-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:
-
-
-
-```json
-// onchain-funds-received.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_onchain_funds_received",
- "params": {
- "transaction_id": "",
- "message": "Onchain funds received",
- "stellar_transaction_id": "7...9",
- "amount_in": {
- "amount": 10
- },
- "amount_out": {
- "amount": 9
- },
- "fee_details": {
- "total": 1
- }
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh onchain-funds-received.json
-```
-
-
-
-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`.
-
-
-
-```json
-// offchain-funds-sent.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_offchain_funds_sent",
- "params": {
- "transaction_id": "",
- "message": "Offchain funds sent",
- "funds_sent_at": "2023-07-04T12:34:56Z",
- "external_transaction_id": "a...c"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-
-
-### 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.
-
-
-
-```json
-// offchain-funds-pending.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_offchain_funds_pending",
- "params": {
- "transaction_id": "",
- "message": "Offchain funds pending",
- "external_transaction_id": "a...c"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh offchain-funds-pending.json
-```
-
-
-
-### 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.
-
-
-
-```json
-// notify-customer-info-updated.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_customer_info_updated",
- "params": {
- "transaction_id": "",
- "message": "Customer info updated",
- "customer_id": "45f8884d-d6e1-477f-a680-503179263359",
- "customer_type": "sep31-receiver" // or sep31-sender
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh notify-customer-info-updated.json
-```
-
-
-
-### Hacer Reembolso Stellar
-
-La integración con el servicio de custodia te permite hacer reembolsos a través del servicio de custodia, como Fireblocks.
-
-
-
-```json
-// do-stellar-refund.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "do_stellar_refund",
- "params": {
- "transaction_id": "",
- "message": "Do stellar refund",
- "refund": {
- "amount": {
- "amount": 9,
- "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
- },
- "amount_fee": {
- "amount": 1,
- "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
- }
- }
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh do-stellar-refund.json
-```
-
-
-
-:::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).
-
-
-
-```json
-// refund-sent.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_refund_sent",
- "params": {
- "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"
- }
- }
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh refund-sent.json
-```
-
-
-
-:::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.
-
-
-
-```json
-// transaction-error.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_transaction_error",
- "params": {
- "transaction_id": "",
- "message": "Error occurred"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh transaction-error.json
-```
-
-
-
-:::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`.
-
-
-
-```json
-// transaction-expired.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_transaction_expired",
- "params": {
- "transaction_id": "",
- "message": "Transaction expired"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh transaction-expired.json
-```
-
-
-
-:::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:
-
-
-
-```json
-// transaction-recovery.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_transaction_recovery",
- "params": {
- "transaction_id": "",
- "message": "Transaction recovered"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh transaction-recovery.json
-```
-
-
-
-### Configuración
-
-Puedes habilitar estos tipos de transacciones actualizando la configuración de tu archivo `assets.yaml`:
-
-
-
-```yaml
-items:
- - ...
- sep31:
- quotes_required: false
-```
-
-
-
-[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.
-
-
-
-```bash
-# dev.env
-STELLAR_NETWORK_RPC_URL=https://soroban-testnet.stellar.org
-```
-
-
-
-### Habilitar SEP-45
-
-Para habilitar SEP-45, configura las siguientes variables de entorno en tu archivo `dev.env`.
-
-
-
-```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
-```
-
-
-
-`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.
-
-
-
-```toml
-# dev.stellar.toml
-WEB_AUTH_FOR_CONTRACTS_ENDPOINT = "http://localhost:8080/sep45/auth"
-WEB_AUTH_CONTRACT_ID = "CD3LA6RKF5D2FN2R2L57MWXLBRSEWWENE74YBEFZSSGNJRJGICFGQXMX"
-```
-
-
-
-`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.
-
-
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.
-
-
-
-```bash
-# dev.env
-SEP6_ENABLED=true
-SEP12_ENABLED=true
-SEP38_ENABLED=true
-```
-
-
-
-### 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.
-
-
-
-```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"
-```
-
-
-
-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`.
-
-
-
-```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
-```
-
-
-
-### 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.
-
-
-
-```bash
-# dev.env
-SEP6_DEPOSIT_INFO_GENERATOR_TYPE=none
-```
-
-
-
-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.
-
-
-
-```bash
-# dev.env
-SEP6_DEPOSIT_INFO_GENERATOR_TYPE=custody
-```
-
-
-
-### 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.
-
-
-
-```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"
-```
-
-
-
-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/` 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.
-
-
-
-```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"
-```
-
-
-
-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`.
-
-
-
-```bash
-# dev.env
-SEP6_INITIAL_USER_DEADLINE_SECONDS=1209600
-```
-
-
-
-## 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í.
-
-
-
-```
-├── dev.env
-├── docker-compose.yaml
-├── config
-│ ├── dev.assets.yaml
-│ ├── dev.stellar.toml
-```
-
-
-
-Tu entorno debería ahora verse algo así.
-
-
-
-```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"
-```
-
-
-
-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
-
-
-
-### Usando API Key
-
-
-
-### Usando JWT
-
-
-
-## Haciendo Solicitudes JSON-RPC
-
-
-
-### Solicitud JSON-RPC
-
-
-
-### Respuesta JSON-RPC
-
-
-
-### Códigos de Error
-
-
-
-## 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.
-
-[](../../assets/sep6-deposit-flow-diagram.png)
-
-:::tip
-
-Los estados en verde son obligatorios y definen el camino más corto.
-
-Los estados en amarillo son opcionales y se pueden omitir.
-
-Los estados en rojo 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.
-
-
-
-```json
-// notify-customer-info-updated.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_customer_info_updated",
- "params": {
- "transaction_id": "",
- "message": "Customer info updated",
- "customer_id": "45f8884d-d6e1-477f-a680-503179263359",
- "customer_type": "sep6-deposit" // or sep6-withdrawal
- }
- }
-]
-```
-
-
-
-Para ejecutar esto, necesitas correr:
-
-
-
-```bash
-./call-json-rpc.sh notify-customer-info-updated.json
-```
-
-
-
-### 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.
-
-
-
-```json
-// request-offchain-funds.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "request_offchain_funds",
- "params": {
- "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"
- }
- }
- }
- }
-]
-```
-
-
-
-- `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:
-
-
-
-```bash
-./call-json-rpc.sh request-offchain-funds.json
-```
-
-
-
-:::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.
-
-
-
-```json
-// offchain-funds-received.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_offchain_funds_received",
- "params": {
- "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
- }
- }
- }
-]
-```
-
-
-
-- `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:
-
-
-
-```bash
-./call-json-rpc.sh offchain-funds-received.json
-```
-
-
-
-### 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.
-
-
-
-```json
-// offchain-funds-sent.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_offchain_funds_sent",
- "params": {
- "transaction_id": "",
- "message": "Offchain funds sent",
- "funds_received_at": "2023-07-04T12:34:56Z",
- "external_transaction_id": "7...9"
- }
- }
-]
-```
-
-
-
-Para ejecutar esto, necesitas correr:
-
-
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-
-
-### 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.
-
-
-
-```json
-// onchain-funds-sent.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_onchain_funds_sent",
- "params": {
- "transaction_id": "",
- "message": "Onchain funds sent",
- "stellar_transaction_id": "7...9"
- }
- }
-]
-```
-
-
-
-- `stellar_transaction_id` es el id de transacción en la red Stellar de la transferencia.
-
-Para ejecutar esto, necesitas correr:
-
-
-
-```bash
-./call-json-rpc.sh onchain-funds-sent.json
-```
-
-
-
-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.
-
-
-
-```json
-// do-stellar-payment.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "do_stellar_payment",
- "params": {
- "transaction_id": "",
- "message": "Custody payment started"
- }
- }
-]
-```
-
-
-
-Para ejecutar esto, necesitas correr:
-
-
-
-```bash
-./call-json-rpc.sh do-stellar-payment.json
-```
-
-
-
-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.
-
-
-
-```json
-// request-trust.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "request_trust",
- "params": {
- "transaction_id": "",
- "message": "Asset trustine not configured"
- }
- }
-]
-```
-
-
-
-Para ejecutar esto, necesitas correr:
-
-
-
-```bash
-./call-json-rpc.sh request-trust.json
-```
-
-
-
-:::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.
-
-
-
-```json
-// trust-set.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_trust_set",
- "params": {
- "transaction_id": "",
- "message": "Asset trustine set",
- "success": "true"
- }
- }
-]
-```
-
-
-
-- `success` flag que define si la trustline fue o no fue configurada por el usuario
-
-Para ejecutar esto, necesitas correr:
-
-
-
-```bash
-./call-json-rpc.sh trust-set.json
-```
-
-
-
-:::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.
-
-
-
-```json
-// refund-sent.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_refund_sent",
- "params": {
- "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"
- }
- }
- }
- }
-]
-```
-
-
-
-Para ejecutar esto, necesitas correr:
-
-
-
-```bash
-./call-json-rpc.sh refund-sent.json
-```
-
-
-
-:::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.
-
-
-
-```json
-// transaction-error.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_transaction_error",
- "params": {
- "transaction_id": "",
- "message": "Error occurred"
- }
- }
-]
-```
-
-
-
-Para ejecutar esto, necesitas correr:
-
-
-
-```bash
-./call-json-rpc.sh transaction-error.json
-```
-
-
-
-:::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.
-
-
-
-```json
-// transaction-expired.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_transaction_expired",
- "params": {
- "transaction_id": "",
- "message": "Transaction expired"
- }
- }
-]
-```
-
-
-
-Para ejecutar esto, necesitas correr:
-
-
-
-```bash
-./call-json-rpc.sh transaction-expired.json
-```
-
-
-
-:::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.
-
-
-
-```json
-// transaction-recovery.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_transaction_recovery",
- "params": {
- "transaction_id": "",
- "message": "Transaction recovered"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh transaction-recovery.json
-```
-
-
-
-## 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.
-
-[](../../assets/sep6-withdrawal-flow-diagram.png)
-
-:::tip
-
-Los estados en verde son obligatorios y definen la manera más corta.
-
-Los estados en amarillo son opcionales y pueden ser omitidos.
-
-Los estados en rojo 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.
-
-
-
-```json
-// request-onchain-funds.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "request_onchain_funds",
- "params": {
- "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"
- }
- }
-]
-```
-
-
-
-- `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:
-
-
-
-```bash
-./call-json-rpc.sh request-onchain-funds.json
-```
-
-
-
-:::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`.
-
-
-
-```json
-// onchain-funds-received.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_onchain_funds_received",
- "params": {
- "transaction_id": "",
- "message": "Onchain funds received",
- "stellar_transaction_id": "7...9",
- "amount_in": {
- "amount": 10
- },
- "amount_out": {
- "amount": 9
- },
- "fee_details": {
- "total": 1
- }
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh onchain-funds-received.json
-```
-
-
-
-:::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`.
-
-
-
-```json
-// amounts-updated.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_amounts_updated",
- "params": {
- "transaction_id": "",
- "message": "Amounts updated",
- "amount_out": {
- "amount": 9
- },
- "fee_details": {
- "total": 1
- }
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh amounts-updated.json
-```
-
-
-
-:::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.
-
-
-
-```json
-// offchain-funds-available.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_offchain_funds_available",
- "params": {
- "transaction_id": "",
- "message": "Offchain funds available",
- "external_transaction_id": "a...c"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh offchain-funds-available.json
-```
-
-
-
-### 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.
-
-
-
-```json
-// offchain-funds-pending.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_offchain_funds_pending",
- "params": {
- "transaction_id": "",
- "message": "Offchain funds pending",
- "external_transaction_id": "a...c"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh offchain-funds-pending.json
-```
-
-
-
-### Fondos offchain enviados
-
-Para completar la transacción y cambiar su estado a `completed`, necesitas hacer la solicitud JSON-RPC `notify_offchain_funds_sent`.
-
-
-
-```json
-// offchain-funds-sent.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "notify_offchain_funds_sent",
- "params": {
- "transaction_id": "",
- "message": "Offchain funds sent",
- "funds_sent_at": "2023-07-04T12:34:56Z",
- "external_transaction_id": "a...c"
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-
-
-### 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.
-
-
-
-```json
-// do-stellar-refund.json
-[
- {
- "id": 1,
- "jsonrpc": "2.0",
- "method": "do_stellar_refund",
- "params": {
- "transaction_id": "",
- "message": "Do stellar refund",
- "refund": {
- "amount": {
- "amount": 9,
- "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
- },
- "amount_fee": {
- "amount": 1,
- "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
- }
- }
- }
- }
-]
-```
-
-
-
-Para procesar esto, necesitas ejecutar:
-
-
-
-```bash
-./call-json-rpc.sh do-stellar-refund.json
-```
-
-
-
-:::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
-
-
-
-[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.
-
-
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.
-
-
-
-| | |
-| ---------- | --------------------------------------- |
-| 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) |
-
-
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";
-
-
-
-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";
-
-
-
-
-
-
-
-
-
-
-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.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
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";
-
-
-
-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";
-
-
-
-
-
-
-
-
-
-
-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.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
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";
-
-
-
-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";
-
-
-
-
-
-
-
-
-
-
-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)`
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
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";
-
-
-
-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";
-
-
-
-
-
-
-
-
-
-
-Receive a JSON object representing an event.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
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";
-
-
-
-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";
-
-
-
-
-
-
-
-
-
-
-**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.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
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.
-
-
-
-| | |
-| ------------------------------------------------------------------ | - |
-| [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) | |
-
-
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";
-
-
-
-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";
-
-
-
-
-
-
-
-
-
-
-Custody Server creates custody transaction record in DB.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
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";
-
-
-
-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";
-
-
-
-
-
-
-
-
-
-
-Custody Server calls the configured custody service to generate deposit address and memo.
-
-Format of `asset` parameter - `stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5`
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
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";
-
-
-
-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";
-
-
-
-
-
-
-
-
-
-
-Custody Server calls the configured custody service to send payment.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
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";
-
-
-
-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";
-
-
-
-
-
-
-
-
-
-
-Custody Server calls configured Custody Service to send refund. Custody transaction record is also created in DB.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
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í.
-
-
-
-| | |
-| ------------------------------------- | - |
-| [API REST](./transactions/README.mdx) | |
-| [API JSON-RPC](./rpc/README.mdx) | |
-
-
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.
-
-
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)
-
-
-
-| | |
-| - | ------------------------------------------------------------------------------------- |
-| | [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) |
-
-
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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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";
-
- 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.
-
-
-
-| | |
-| ------- | --------------------------------------------- |
-| OBTENER | [/transacciones/:id](get-transaction.api.mdx) |
-| OBTENER | [/transacciones/](./get-transactions.api.mdx) |
-
-
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";
-
-
-
-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";
-
-
-
-
-
-
-
-
-
-
-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.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
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";
-
-
-
-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";
-
-
-
-
-
-
-
-
-
-
-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`.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
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 65d2bb536379b5d12d628e73d274595b0fd0e945..0000000000000000000000000000000000000000
GIT binary patch
literal 0
HcmV?d00001
literal 565132
zcmeFacT`jB);$~*6^{j?QdEk93W`z`q$d_27Nm%Ph!Bc&=~6=oRyxrG3eqAVq97nj
zhY*kw1td~KkJ3U-gd_wKlKeJu?z#8AFXz8+jIYTUDkNm@XRl|KIp^C1Ql(4%GqkLp*8G{!Qw#(
zg$R6Ny)Ppl%%=5T2Z7GU#Yn9G&cTa%0_(pccsOh8`tR`n+5Qjb;rlYVVg1kCzfE8N
z4bZt$!Rx;hc5t8e`tO{5^80dr@6K;$`yD%=->CrfJ5hsvr-I+9;CCtj{Z0h{l>QAt
ze^87m${7wb`k4^>ORDQ-|nd{3uKQSdewdUmY-vm98{;f~_#yYvz~rf*;TN749#-9L%b`*#0RlKK2Z^q!N|I8#c#z`0o0>O
zoia+n`=#~Zr0#ChN)#{j=4k!Pq7F8$7+84
z7}gZo{t=`UoV3B2sj;0)N^}
zk4{d?u4}Vets2AH{5|b69%Ys@y)!d2QjX$;j}b(zpoPQYVq$v*UJgc!D0I-s1YEgr
z5etjO@~yWBP+6p?_TYJNCa%0ZX-Wm0B^j$XwXkq14TH(4voV_S3l9%({CH410kJr1
z;hhz+^tIuu*ijZIltsjGpZ&9I91Yn0
ztb15c4bqPO{`@rGl%b(vr;Xyp^?xg5pkdOsQ70zU*Y_hmslL8`ecRWT%>k~HIyyQ^
z|6cb1SRJR4@xv==%Y$>%O!m~#Sp4Y7GO(JGoB741rOyFlcb0v(OyyV(Q9YM6*7b_8
z6aZ|=$!;7*AP`eOe|k+T6_w74BKfEU0-@7c`Ep`nqRHq|nt_a8)lhLo#S0+1uEpCu
zjz~sbDkP@tSI4wU5U9i06b(eG{VDcUJO?U5YlIMAs28AnX}vQrv;?yI8=^H3aN6PO
zAd|tvw*3J@5Del2^=cF+8n3LWsR>_UF6}6ycIvYwAShCNeEi#)Ie&JZwdJ~|8nph8
z9Ad~ym$vXUWRhrq5~`y*db
zDHMa9NJ&Xa9_7(hgDguKyc1oKquY{rsD{)#6L?*hkP}(U{^&&TxJ%)mz(ZhR
zq1IQa0j(zfo5BSoAtCdmyijU%Wh4*2?i%5Qp{jsAty7(8eD7XGR8r^Wo=NQ4Ks%~y
zqm?-b4#UXkNJ_m41x&(SCZL`_u1onDN*WiNX#
zdylGE1Ucve{l~(>ha}CKs-<0t$0mRz>fPVldqY-7@+cd*$9LVyj9T~A?R|G#k94~h
zfkNT4zWanbJNvE|{W_Be-)+oXGDsPW=jW0d1`RQgtN-f^
zt1rAiz8WEb7j`iCI|y#OGvQ-memb>U!#OTWOd!B-KEL#&=It8<-w;MC=tF`c58gPe
zEc6PjHr-4_5trVt#3U^lng)MbIrANnu#p
z(WPwQZMUn?Q(8m)_Pgs3cVD%CeY}+pJ~Z3>1a#
z%^?=Tb97sG-{pnifD+fiVg(nGlv;po#jPw{(SSk=cYMV=#WGix$(YXSqZr)fTYClu
z1{y>0gY%^LnZs>h40HmbshOu`ev3N)g1NZZaWz64qNbKqDS^qDRTagk)_in<;JE8u
z7wEh1e@05f$G;+_6Nr?lGp)PZ7lQ0YSCe&?en^{$f_1{JOfM
zd7?qW4mY|2#uV=Mg(6wX05a$p9l3?$aS{2x2G^}Rf%v&dd&Al({{gq&x@*g*l%c9^
z6Z9#Ajb=BihU9npp!Kqp^CH~Lbz7wiw6Cazy1B_=Lpd6&&M-RN&`Aa(_R{o{aFkYX
zV&Q4uh;Li~S|r2Lz9adDocgHc@*|qT>_zwafNnOhyUKY<6~}cXpK{F$t-Irz@b8Mq
zrt^!vGr7$5z1uTQRNH7jE0o7YCU@6|3tS;e@3j`%&ij);7G{J!5eE_5MgAkp97`?4
zac^plaf!sHR?~B=pwUSuC#R{gu~+n@-WmQ%g8lA*!ac7rrrpe9EY^yTLk45iH?BD3
zF0NbaK{bAM^s|)#)Zwm@h*t!ujU;n(a}%Pfsw(-9c0(OC9vOp@*LF--41N)aV=x%X
zg}_y1N=`(!Ls8u7yW00D(X#;&74`zn9ybM5HzcW0BnppxoE)5IeRwgdA&$mxThI0&
zpCft#*OQO*S_$7rD=xJpDs*O64tezV^}VQ+cuKR7W_9X((;D_Pp6>%3;R-tP#nuPs
za^>PqZs);tLfc=mb!O`T5OEp(LPZbmZ`H^?>9Z+J5K&WBW*)3>Dk!<`Icps3=(V5P
zsgb#A!4K%umN87%w?e;=s>HnkfK%7Qa)ai@
zAH!J0KO0f`^@+F|Addhw*d$&`8FEq&I!D5l@|WNtG5Ar10@!WH`PqE4Jh~QmKw%FX
zyTj7bvhhx*-MsgO`x;7|Z&P<)Q|g_Sb4vtFM;LhgKWvv-dm7)ju!t$x>Ev>mxWodul~wk@n-iIm)2-V3V_z2l03&;rsnfmUXUEEz-m)16gSi0J
z#eZ=9VZ$X{!{ohHEG4WWy5n`hNx8V1(o(ZZYvDV*WB?gXu~Jk$FB3=E$JuvUcC?4*
zF3(U9sX52*NSS3VB&>f}M;daYne`qe)(2l5<(d;_xD!B(Or42RLutL9>ti#i
zSKx3)MeaswbW|UaNX%*a;nc?j;I`Bm_|dj991gBE^3mPhU5L;UM_IpmmKnrIyxIF>
z{`e{kB1#>#77~N2I4H4llMvlsH}%i?-z+V!t5wcwm+kJRGCNn}1;Ed4;!v?&(Xa^Z
z7+GX$R_D}S!n!V5%L6o~4q%y`nYkOM;PpURDC@=|n6KN+OA<|sSSbZ!UR8$%yo|pQm+Dtg1N8|dQz>`EhBx@9e5Y&4?$*rdEKsT2*g_UGSvGo
z2Et)8JHLFnv_8o(l?H%^hw}bs1pyjqe5x)^PGnRjof8T@IlYRPDU{a$l6pNKn7Zx)
zY)m5nczs}3c=pVYhiV<%3J%Y4h?eCvHa7AePL%;56o4DFC^w|Ny)+P|N7g;ajm;z(
zo9vxi9&|8{+R;}5Zg-w}WXe33!!Eu9?4o~FTJm0Uv?5aLle6;iPYd&bw27;gm6f^3
z0=302@iMw&H2@o3_t2mF0BHA)-xu}`ksJ}G3eHm4o>-U*Wb3O|mT7>epM47OjPftFA7b^g-ny9@NQR}FcvZrXVQ3yqdVc0-!{
zEc`C4TO2`4&sS-XhPwKtU*$=9YzRo$Rt`U?K$=vRK=0w@AD^fJ*lljY9P`5{&y>td
zR$@i=Vo0Ive6uI(hxKX=l9QF91K1=RFD54T%HsOw|`#0Hcm6sllFy{qx|GC)2m
zh39#7Hcy_914!~Nwrxc^gRXl)?~*mQ-Pi}-jTS||
z@UOCxljR;UJ;camS~mdHt;I+<4g>3!xZ~-WQ`sCBTLJLsYw-mI1;_2_XbJ7hrn%>7
zEiCzU%YaSyYWzhgE(6Xq?!C&btbzCe0Ps~S$z9>GTRSfBb)c4hgl9KUQnZ{}_nl*&
z!dfeIGiLifb})KpfUr(p7)3*$w@G@hKkiBHC$6-ODp;elJ)AY^Ofv&3{I}$9by^Dch
zQnCy4Pqa!VSEsLQgc~RA=uh5W`o^w%u(iZ)8mxjjaufn+M0q3qhUr?DfYZ1bgJGD5
zlQL}tLNo{wzky07U=p`{&C?O&0O+{U_eIbm)Y_z!6wkCid{I(Wz**xJoMDktxvdtU
zcUOpPPH5%M=9+qd!mn=&319(F`Qu<}AwYGF_y#*$ZSb(VbLth~i%_?
z=*Sq#fgW+L1vX<3L+2I?$gL(sr^wr|yP6VUZS>^QyAh<6gd}+RsIF{{!Nri>r$~c?
z?@|vzoKjCqIC#_52&=GJjv`S<1DOAH^VS3Gl9G~V)2%mU$|cFwfW{=J2L;!$Km26r
z=uqu(dBbueWF4VQUq>VO;ar{o|01}3c0j6QnB}Np9G*x1yoN|jnm;oU1d!QBI*#Om$
zN>~LgD+8+q8^9}$QFDNXK#W@^?9akPs0Fs}M=v3yCSqV|5$uK&G=n|o7J8}WrPE6t
z)_6Dks5fgo5q|svWlyyA1t@pPKA5`_ly5Ix4tb%;<*w|HtN@_NQX5boQXGp~MUf3W
z)iY;~qoXTi&`X2!FGdlTW7ze4G;H8%O#0@C_D(S+7OTcT26Da!e3r^&15${y#JxF-
z`}F8!l{jmmEc9g1kRn?vx%$xATjqd-@lN~|{JP0UbKT(-VIr@wQ5QUdX*^|5Kg7i-
zQUhexZ@?|@&T`s-p&Yhx(7B;K@&m_N9O$?}k7q_R`v(TDv7}KWqA655_6`t~p;2s_9T0i~2*8qtAW_>C8Dr20lepe2t
zGxDhA1qbj(_+x_{6TT*C%5X7%70d`X)i;WW2n_ACYfB2Su%&%jPN}Io+sf`Vgr1z+
zzs-BoqLO9Mtxl|k@bDqfq
z^qDB_lhAl$mYVs>E)U;`
zP$`f8Z(RZFo)h#RoSg8NZ0-8#aDn)}pFlnm;tkC(p6_>pUk~8|;V=S55pqdXkvhuU
z+}xv0?5e7&MzPM2rJp}|D*>&Dz(7FxtJD98XMzuLk2go^CP_l#e*Z~8J=HZ=hP
z`=c#d9IY)af|N1%zwWFUn8&JfPb6fw_E(%6u;f#-?sRjE&jH}Z@2i{6u+~@zfJMmE&gqb-`V1CTl{v5
zzfJM~!)&2^?C&;&cm{9$f(zRde)Rx6P@Q8(kaIEQxxM9mKd>z<%f2}hpZy|74AU0M
zoOfv}-qX1PRsZ*AS4|j`JvuD<#D=e$HJ$gbL7K24kwf&EbnPd>>D;uRL1Esr^kb+e
z&sV0txU~0q8g^D5{jXNPGkzW~iLpr<7Stm|fd6hVp(aoI7ZLtG`LKCp>-@x
z!{OS-?~}c#pGN)jl7+8eyt&5WDRYHv6cv?Ep^c*!!(AASR{y$`UtV$(tVaL?i~IZ^
zi}N>w6e}=1P(`K4>9I?15yMqcg2AAsoUL3&z?7yTqx(^ZLi+Mz@uDhP!`Gjf}GlF$s`V2a-C2~X7Ish|9QZdU|YJ_
zJ=GP)v46d)e-JwWf44o8H$Z#++Ek?4L{Phy4@@HF$uDKyqf*O0krCWmsup17A9#Qv9kQ*^cI_u^2O@6n@FSaZUgh2VctTsDbTKdwz@5j;?
zoGHWIK!~5C#~ac~DA3UlOA>IJIW^b45WzY-jaoKZn~WIt>9KIi-eaJ4NPDr@e(Hvh
zI~o!J>+Z?7>}*TZ>@;dkQ7x36p;S=~(oV1@ZltUB)gakNZ$leaVuFGvUO2rrP)(f?
z{be;9*%g)Jf7=fPgu=18ITSW1hbM
z8z+GAzsB;Imb2z%7BBJt`mLC3VBOh3W2u_|U7R9o=Ycb?W(un0l|oNiRVrHr{&)ma
zxvfP=8I9AFkCkbc(e$5{omhz3cel
zwhF9e8@2rupcy%`%$g}QBw7Vn4IyF&Lug-J`aU@5+HeZ2sycE_^EzHQrCVrCd`(HD
z)UYY9@sxqGLNy4L_d@_xF6%~aOMClFjhLw$J>AxMToHG(u&!+nrZMX#&Wv$fvh#CV
zz_3L~jcxto`u(a5)@$3`Lxuq)U_WH@O4iPmHm$CcPvP=g?S1Q_+oSMl|-kF?d<@T(xjbUH3X)}1$(=Q6roAqPGibYyM{l`sEtlg(j$
z_4#sTTEb{&9~A=m`oiBXnI|K&W>C?cogQpb3DJ;OHU)U?LI$rUZ!wsVYqECVP)s)e
zg_^NHuXF(8B%LOP+NKW=VGxuGm+7vzQ>wV-tM&F$t;;~>SGYez1>#0ZIjAXSpWlYB
zWkdd!Cwn2$A4YGf->wMO2X48zS$WsRo&D}(+i?i)=cnz_v`25u)fHEMgi9LulH2k%
z4IiE%1&+oxh8Cf;Zl=kkdVSi~NOMTEG81XQ+2i9f)ALyw#+LQRa#F8#9b&1lRCV6p
z)$*}y_KPOAr&oJ^9^GRdH2$pej6A%i+8H5cVg`X7XIN+j`1uK)8}5e4qOTU1SGOTK
z*$T+Ffe+O@KibUtpc;$7pVIL1!wQLg&SK3D=1h!=n_2MKQ&?2x&ZB6j3P=SZGZh${
z%9PBd9h5BDx}NCY`OWkAYy5
z+{U?II2PJ)3dWHfMKpvgkJkVmSe{QMYdupDZy(l@F`Y5msU%a0=_R9#BV<0vm#we^9zcu4uGX1Y)`{j5;h*v4jlL0QS9;@M6*xOFyICo|YU3B(^Kq4U>F@_+j{S)dEdOqW
ztr-I5yPlzab(W2(mY>K!s_`G-msvSd4_<7e>?~?0ry(^)9mK8Dbu%ZON7`H3wijlgRG3t$OJMh=){7k
zsqO)q%AYe&3Nz{^E|!p_dZA29Mx`5>o!c%dZ&~_It#k$3ODPWrVmE#J{WZxn?8j~Z
zBHc~!BdiqgXTaGFp+9J~#zm{8R#R5EesYLw_jjfRVm)mB#QAvN2!Fn3PU^R@`}M4Z
z>b|Hy(bReGyUQw0knE%8mnzdHQa1~hN<(k+*56f2__5?LAGDmLW~i=JeIood9B>mq
ze1mVoo(!sOcdqH%r)ozRql5L>HzR#@DvZNjBSJm!3?dwkP&nTtZKDy_!gy0E!@2|H
zN|*A5K(hf!vMk!vB9&G?8t0~QMqM8|O)B6YY^z&f4h6uiE+T`fTk3uUoyhWRMoN+i
zoEy84k_BS^a0n~`Q+RJ7HLB(dImX@xJ{CODDALS`Qtx#wP_=x2D7wO^z*3^h5tGPv
zlC|HP8ETBtBYH9Vo9%^s^Mdv1SF~x>AakQFY
z1!)8!FKJ@+(5BoziG5q3{Hm_F^9+Yke(MLX{#eA
zi{m>GM-4CM7|f3fD1KO!)JpJQ!OKmxqYz5&tnMpQBsN@b7;VIQCNOt}z?tYSW{nj5
z7fu>A-UW{foA436`|v9424a_mr|>DOUGE8YBw4wQ-7WXN0Uj%M&`Q|$EBO0xcXxMB
zP%|UecYIFl59?hBh3L{o$k+Z-o4Wg5z*uzo^h-Xt)I1(O#Sivk8Wnmkjcod0sC&F@4RiX`js8Hz@Q!|T_35=^Jml6O-;xi&^V~5Iq~1-R
z@$PM+npo!Wv&Dq_*UW~C*KVS#Ejs=w;etx9`o?F{hc)g$x5qf%YrXLF!Mg*G^uzh@
z6+DIsFvTjW9m!wrwRa27|M>i4@xYloZysgCp7|7@N^hs|X~
z1?yf6OfcD{B6*n~St9Q}`&E?`(o3#r_2~oqNN{%3D6OXnC(aW`!S4Ga-*bO_o^$TO
z7#F6er}z68%apxsm-=HlNi11n!({BlMY&j(oiZy&YpV~mA?WexvRog@o#V-bXg(cr
zyL9D+rURZ`&q#4%dYD4I^uBt9(D~>o;I$Jqs#&d%wu=ZK;=ou#YqLvUhgWg=p5f%H
zNWXJ*^Vak~3$zRK_#?K6x@{lk#ocXZ8yJv~K5$lD52q0USpBlqCeo!m1%M)h-}C*3(77-35k}*I
zI$^;Ue9AD{z=!c@9Z_V@iI~vCV?Sr>?pOGVBGvC8%6-a_bkhX$UCjlLSHk(<#(6D<
zP%^eWEwficiuu~MXX=&+QhczF_vqn(xvCL$))9%hh+rtA%fw}QVZ1RUrslXpk|51X
znU(iU`h|4<#E*SWsm6RS&<$c@SFEh0X#qY+B(jlaG~t>a-tH7DtR`Au=I5;PxI&@X
zUUd8M1|?(M!XVnW;nN>QHjOt3wrk)BK$Nu)g%8oS4JF?Is3^!J`e1Na)-mDw8-8_?
zLIhIK!dIRkk=A%
zJdd7lmKN1IPsCT%ouB;pbQcKyl0He`&p^MQ5}QT+cqGy@7XYNi9Me2AA;#?7T>j=h
zCjicz-@i?LvdRj)fc$bKaW7{#1O1KZg9T73(f?(LX@bb1!LQfxC(c(%hA#ccG_Wka
zb4ft!=h=2ld)a(M=xVXtFE`irR&Qa1FLq2x>1(p)HSlc-sk0hw-IH2ipY-}18W(o_
zQ;)Q>#>O0{ugRvV(!+V_&`*;W9%9jYFM}cQ;zH91f72MxSxNhl0r#@(r-B?odqF?Z
zw!z4vNEjuDe;y6t;!!JjrJY#{gtz`o^cg%CtT+5_Zr-9|WnP|;AHorHNeWJvG`6m4
z-awPCP}7r$9&GY&Qbge&0yEdI8L_Yvp9SY)bj3&1C%i-cYLvzZZHoXrru%m16uYjW@0LD{U?J-m-C0fxZ
zJqQp!_i%4jU%)Yh3E5y_@#Aycz>h#cD~@)ys@uM91fIfCYshCI&HE
z2ufi%b;(S)cWFkyWC+qSo({?=S&xS?=1*)b4$o-Kcl4=BK}ymYjBH20h>DKc@{CZ!
zM!!V-F;u|Ax+Xt6ActD%6`E(P+mv
za>!MGk>?xDw!Py&$MvLctA|4+T|f*|b1PFVn7aCB_2{#cg(%KU;c~?kDfc=SzQ#E_FxfqSv^FXb!Vz0JA5vFQ-M9k$JxJ_H!8^sbgwcN45;#fk^o{D
z{>U1Si2YRJ`*~@TfR<5!ewUK)R%hYQX)1pZJ_
z_CBcF*G+j30oY=*v482)6&Ft)U;+~v!^^8lo=?$w6}dziu~uW1
zdk?=zs!5*E*Hl{DpdF4w0;p6Ldw6A2(7C_pbW8&Om9~ub@q^=zQY-5B6IJi@8g0KX
z5yub6ZDd(DV3TzxL-?X$FYi8l3A^D70OE%daX{(mY4fF2kbBzpoTIDn(CAm{IQP8*
z^XdNP?a7oqei2-Br7kveXrR%ipx_K~H
zoIPfLepZq_VV{d1=Zuu|Z$O`=CYcyB)n1pCsapAbIig!0(shg~>DS_Stc+GV;Nez*
z@*v%)qSmnY_s9vGML;6`VM8AmZoz9pg1q(p3h*ljrZ$81Ea^zTkBQ_XiuC8TK*wkuxg9Y$w!Hg-CPSb2VM2yP^ar
z&vxl!%cO!E