CLPX S.A.
clpx.finance
Identity — verified, not assumed
These accounts are the ones clpx.finance declares as its own in its
SEP-1 stellar.toml,
resolved live at scan time. An account cited there as a currency issuer is only
attributed to this anchor when the issuer account's own on-chain home_domain
confirms it — a cited issuer is frequently a third party's, and reading one as the citing
domain's own is how a shared stablecoin issuer once got credited to a single business here.
- GDYSPBVZHP…3QUX5G — declared
SEP-1 resolved successfully at 2026-09-14T15:25:29.776Z.
Settlement record
| Account | State | In | Out | Last seen | History |
|---|---|---|---|---|---|
| GDYSPBVZ…3QUX5G | dark | 7 | 0 | 60.3d | 65 obs |
Liveness is read directly from the ledger and cannot be self-reported: an anchor can keep a status page green indefinitely, but it cannot fake on-chain silence. Dark means no settlement in over 30 days — a fact about the ledger, not a claim about why.
Trend
No state change has been observed on any of this anchor's accounts across 65 recorded scans, the longest unchanged run being dark for 10.8 day(s). That is stability as far as this record goes, and it is bounded by how long the record is — observation began 12 August 2026.
Capabilities — declared vs observed
A stellar.toml entry is a claim that an endpoint exists. Directories publish that claim
and nothing checks it. These are the results of asking each declared endpoint directly, at
2026-09-14T08:22:06.623Z.
Every declared and probeable capability answered.
| SEP | Declared | Observed | Latency | Detail |
|---|---|---|---|---|
| SEP-6 Programmatic deposit & withdrawal |
declared | answering | 517ms | 2 depositable, 2 withdrawable asset(s). |
| SEP-24 Hosted deposit & withdrawal |
declared | answering | 213ms | 2 depositable, 2 withdrawable asset(s). |
| SEP-31 Cross-border payments |
declared | answering | 160ms | 1 corridor asset(s) advertised. |
| SEP-12 KYC |
declared | not probeable | — | No public capability document is defined for this SEP. |
| SEP-10 Web authentication |
declared | answering | 128ms | Answered a bare challenge request, which is the expected behaviour. |
A failed probe means the endpoint did not answer correctly from one vantage point at one moment. Geo-blocking, rate limiting or a deploy in progress look identical from here, so this is an observation and not a verdict on the operator.
Machine-readable
Everything on this page, including the observation history, as one document:
Scan of 2026-09-14T15:25:29.776Z · verified against stellar.expert · methodology · dispute a figure on this page