Revise README for EHEPS Stellar Wallet integration

docs/data/apis/horizon/README.mdx

@@ -1,42 +1,93 @@
 ---
-title: "Access Blockchain Data with Horizon API: Query Transactions, Accounts & More"
+title: "EHEPS Stellar Wallet: Access Blockchain Data with Horizon API"
 sidebar_label: Horizon
 sidebar_position: 10
-description: "Learn how Horizon, the API for the Stellar network, enables access to blockchain data. Discover endpoints for querying transactions, accounts, and more."
+description: "Integrate the EHEPS Stellar wallet with Horizon to query accounts, balances, transactions, payments, operations, and donation activity."
 ---
 
-# Horizon Introduction
+# EHEPS Stellar Wallet + Horizon
 
-:::info
+:::info EHEPS Production Integration
+The EHEPS Stellar donation account is `GDQ75AS5VSH3ZHZI3P4TAVAOOSNHN346KXJOPZVQMMS27KNCC5TOQEXP`. EHEPS applications should use Horizon as the blockchain data-access layer for reading Stellar account, transaction, payment, and operation data while maintaining an independent database for donation reconciliation, audit records, and historical retention. The publicly accessible SDF-hosted Horizon historical dataset was reduced to approximately one year beginning August 1, 2024; therefore, production EHEPS systems that require long-term financial or audit history should persist relevant blockchain records independently or use an appropriate data provider.
+:::
 
-On August 1, 2024, the publicly accessible SDF-hosted Horizon had its historical data truncated to one year. That update optimized the performance of the publicly accessible Horizon and ensured a streamlined experience for all users. Consider third-party ecosystem providers of Horizon, which may provide a longer history retention window as well as other features.
+Horizon provides an HTTP API for accessing data from the Stellar network and acts as an application-facing interface between Stellar applications and the underlying Stellar network infrastructure. EHEPS can use Horizon to retrieve the current state of its donation account, query balances, identify incoming payments, inspect transactions and operations, investigate failed transactions, and monitor blockchain activity. Horizon can be accessed with cURL, a browser, or a maintained [Stellar SDK](../../../tools/sdks/README.mdx); for production applications, EHEPS should generally prefer an SDK for transaction construction and submission while using Horizon directly where appropriate for data retrieval and operational diagnostics.
 
-:::
+## EHEPS Donation Account
+
+The production EHEPS Stellar donation account is:
+
+https://horizon.stellar.org/accounts/GDQ75AS5VSH3ZHZI3P4TAVAOOSNHN346KXJOPZVQMMS27KNCC5TOQEXP/payments?limit=50&order=desc
+Horizon: https://horizon.stellar.org
+
+Horizon: https://horizon-testnet.stellar.org
+Stellar Network
+      |
+      v
+Horizon API
+      |
+      v
+EHEPS Stellar Indexer
+      |
+      +--> PostgreSQL
+      |
+      +--> Donation Reconciliation
+      |
+      +--> Audit Logs
+      |
+      +--> Monitoring
+      |
+      +--> EHEPS AdminOps
+      |
+      v
+Secure Signing Service
+
+```textcurl "https://horizon.stellar.org/transactions/f9d806e098ddb4596e56e2e60a776dbae0c6ca2329f5a276b9abf8edf3fa99ce/operations"
+GDQ75AS5VSH3ZHZI3P4TAVAOOSNHN346KXJOPZVQMMS27KNCC5TOQEXP
+
+Transaction:
+f9d806e098ddb4596e56e2e60a776dbae0c6ca2329f5a276b9abf8edf3fa99ce
+
+Ledger:
+63886144
+
+Status:
+Failed
+
+Processed:
+2026-08-10 10:24:30 UTC
+
+Source:
+GCWZQF…SOIVML
 
-Horizon provides an HTTP API to data in the Stellar network. It ingests and re-serves the data produced by the Stellar network in a form that is easier to consume by the average application relative to the performance-oriented data representations used by Stellar Core. This API serves the bridge between apps and [Stellar Core](../../../validators/README.mdx). Projects like wallets, decentralized exchanges, and asset issuers use Horizon to submit transactions, query an account balance, or stream events like transactions to an account.
+Sequence:
+256067419066462063
 
-Horizon can be accessed via cURL, a browser, or one of the [Stellar SDKs](../../../tools/sdks/README.mdx). To reduce the complexity of your project, we recommend you use an SDK instead of making direct API calls.
+Max Fee:
+0.00003 XLM
 
-This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://stellar.org/blog/developers/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md).
+Fee Charged:
+0.00003 XLM
 
-Before we begin, it's worth reiterating the sentiment echoed in the [Core Node](../../../validators/README.mdx) documentation: **we do not endorse running Horizon backed by a standalone Stellar Core instance**, and especially not by a _validating_ Stellar Core. These are two separate concerns, and decoupling them is important for both reliability and performance. Horizon instead manages its own, pared-down version of Stellar Core optimized for its own subset of needs (we'll refer to this as a "Captive Core" instance).
+curl "https://horizon.stellar.org/accounts/GDQ75AS5VSH3ZHZI3P4TAVAOOSNHN346KXJOPZVQMMS27KNCC5TOQEXP"
+curl "https://horizon.stellar.org/transactions/f9d806e098ddb4596e56e2e60a776dbae0c6ca2329f5a276b9abf8edf3fa99ce"
+# Approving workflow runs from forks
 
-## Why Run Horizon?
+You can manually approve workflow runs triggered by a contributor's pull request.
 
-Running Horizon within your own infrastructure provides a number of benefits. You can:
+Workflow runs triggered by a contributor's pull request from a fork may require manual approval from a maintainer with write access. You can configure workflow approval requirements for a [repository](/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#controlling-changes-from-forks-to-workflows-in-public-repositories), [organization](/en/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/en/enterprise-cloud@latest/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#fork-pull-request-workflows-from-outside-collaborators).
 
-- Have full operational control without dependency on the Stellar Development Foundation for network data and transaction submission to networks;
-- Run multiple instances for redundancy and scalability.
+Workflow runs that have been awaiting approval for more than 30 days are automatically deleted.
 
-The Stellar Development Foundation (SDF) runs two instances of Horizon:
+## Approving workflow runs on a pull request from a public fork
 
-- [horizon-testnet.stellar.org](https://horizon-testnet.stellar.org) for interacting with the [testnet](../../../networks/README.mdx)
-- [horizon-futurenet.stellar.org](https://horizon-futurenet.stellar.org) for interacting with the [futurenet](../../..//README.mdx)
+Maintainers with write access to a repository can use the following procedure to review and run workflows on pull requests from contributors that require approval.
 
-## In These Docs
+1. Under your repository name, click **<svg version="1.1" width="16" height="16" viewBox="0 0 16 16" class="octicon octicon-git-pull-request" aria-label="git-pull-request" role="img"><path d="M1.5 3.25a2.25 2.25 0 1 1 3 2.122v5.256a2.251 2.251 0 1 1-1.5 0V5.372A2.25 2.25 0 0 1 1.5 3.25Zm5.677-.177L9.573.677A.25.25 0 0 1 10 .854V2.5h1A2.5 2.5 0 0 1 13.5 5v5.628a2.251 2.251 0 1 1-1.5 0V5a1 1 0 0 0-1-1h-1v1.646a.25.25 0 0 1-.427.177L7.177 3.427a.25.25 0 0 1 0-.354ZM3.75 2.5a.75.75 0 1 0 0 1.5.75.75 0 0 0 0-1.5Zm0 9.5a.75.75 0 1 0 0 1.5.75.75 0 0 0 0-1.5Zm8.25.75a.75.75 0 1 0 1.5 0 .75.75 0 0 0-1.5 0Z"></path></svg> Pull requests**.
+2. In the list of pull requests, click the pull request you'd like to review.
+3. On the pull request, click **<svg version="1.1" width="16" height="16" viewBox="0 0 16 16" class="octicon octicon-file-diff" aria-label="file-diff" role="img"><path d="M1 1.75C1 .784 1.784 0 2.75 0h7.586c.464 0 .909.184 1.237.513l2.914 2.914c.329.328.513.773.513 1.237v9.586A1.75 1.75 0 0 1 13.25 16H2.75A1.75 1.75 0 0 1 1 14.25Zm1.75-.25a.25.25 0 0 0-.25.25v12.5c0 .138.112.25.25.25h10.5a.25.25 0 0 0 .25-.25V4.664a.25.25 0 0 0-.073-.177l-2.914-2.914a.25.25 0 0 0-.177-.073ZM8 3.25a.75.75 0 0 1 .75.75v1.5h1.5a.75.75 0 0 1 0 1.5h-1.5v1.5a.75.75 0 0 1-1.5 0V7h-1.5a.75.75 0 0 1 0-1.5h1.5V4A.75.75 0 0 1 8 3.25Zm-3 8a.75.75 0 0 1 .75-.75h4.5a.75.75 0 0 1 0 1.5h-4.5a.75.75 0 0 1-.75-.75Z"></path></svg> Files changed**.
 
-- [Admin Guide](./admin-guide/README.mdx): how to set up your own Horizon instance.
-- [Structure](./api-reference/structure/README.mdx): how Horizon is structured.
-- [Resources](./api-reference/resources/README.mdx): descriptions of resources and their endpoints.
-- [Aggregations](./api-reference/aggregations/README.mdx): descriptions of specialized endpoints.
-- [Errors](./api-reference/errors/README.mdx): potential errors and what they mean.
+   ![Screenshot of the tabs for a pull request. The "Files changed" tab is outlined in dark orange.](/assets/images/help/pull_requests/pull-request-tabs-changed-files.png)
+4. Inspect the proposed changes in the pull request and ensure that you are comfortable running your workflows on the pull request branch. You should be especially alert to any proposed changes in the `.github/workflows/` directory that affect workflow files.
+5. If you are comfortable with running workflows on the pull request branch, click the button in the upper right corner labeled **Awaiting approval**, which will open the **Merge status** panel.
+6. Find and click **Approve workflows to run**.