> For the complete documentation index, see [llms.txt](https://stellar-developer-tools.gitbook.io/anchortrace-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stellar-developer-tools.gitbook.io/anchortrace-sdk/guide/demo-from-real-testnet-transactions.md).

# Demo from real testnet transactions

`fixtures/testnet/` holds raw Horizon responses for real classic transactions made on Stellar testnet with throwaway accounts (see `fixtures/testnet/manifest.json` for accounts, asset and hashes). The anchor-side SEP-24 records in `examples/` are **synthetic**: no real anchor produced them. Each of the 18 cases in `examples/cases/` pairs one synthetic record with one recorded transaction, and `examples/reports/` holds what the engine produced:

| Case                                                                                                                           | Outcome                | What it shows                                          |
| ------------------------------------------------------------------------------------------------------------------------------ | ---------------------- | ------------------------------------------------------ |
| `matched-withdrawal`, `matched-deposit`, `refunded-with-onchain-refund`, `reordered-and-duplicate-updates`                     | matched                | the Stellar leg agrees                                 |
| `wrong-destination`, `wrong-issuer`, `wrong-amount`, `wrong-memo`, `failed-onchain-transaction`, `error-status-funds-received` | discrepant             | each is its own finding with the operation highlighted |
| `ambiguous-multi-operation`, `status-history-conflict`                                                                         | ambiguous              | 60 + 40 to the anchor is not one withdrawal of 100     |
| `unsupported-path-payment`, `unsupported-claimable-balance`, `unsupported-soroban-transfer`                                    | unsupported            | real chain forms v1 does not interpret                 |
| `pending-awaiting-user-transfer`, `pending-external-chain-confirmed`                                                           | pending                | status drives what must be on chain                    |
| `insufficient-missing-evidence`                                                                                                | insufficient\_evidence | missing is not a pass                                  |

Excerpt (`wrong-issuer`, run against live Horizon testnet; full transcript in `docs/evidence/cli-live-horizon-wrong-issuer.txt`):

```
Transaction syn-wd-001 (withdrawal): DISCREPANT
  Operation 21782411972972545 paid TRACEUSD:GAZ3S5...ER6ZII but the record expects the same code from issuer GC7Q2W...JRJD. A same-code asset from a different issuer is a different asset.
  Evidence considered (linked by stellar_transaction_id):
    [conflicting] payment op 21782411972972545 in c44916ee...e810d9: 100.0000000 TRACEUSD:GAZ3S5... -> GBC4Y6...J7VI memo(id)=1003
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://stellar-developer-tools.gitbook.io/anchortrace-sdk/guide/demo-from-real-testnet-transactions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.