Stellarport
stellarport.io
Identity — verified, not assumed
These accounts are the ones stellarport.io 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.
- GBVOL67TMU…225PL5 — declared
- GC3M7GD3HN…YQMALT — declared
- GC45JH537X…OVVIGD — declared
- GDD7ABRF7B…EM2TCP — declared
SEP-1 resolved successfully at 2026-09-14T15:25:29.776Z.
Settlement record
| Account | State | In | Out | Last seen | History |
|---|---|---|---|---|---|
| GBVOL67T…225PL5 | slow | 30 | 0 | 3.2d | 57 obs |
| GC3M7GD3…YQMALT | dark | 0 | 0 | 67.5d | 57 obs |
| GC45JH53…OVVIGD | dark | 0 | 0 | 67.3d | 57 obs |
| GDD7ABRF…EM2TCP | dark | 0 | 0 | 68.3d | 57 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
4 state change(s) observed across this anchor's accounts, 2 of them to a weaker state.
- GBVOL67T…225PL5 went live → slow on 2026-09-14
- GBVOL67T…225PL5 went slow → live on 2026-09-11
- GBVOL67T…225PL5 went live → slow on 2026-09-10
- GBVOL67T…225PL5 went slow → live on 2026-09-07
Observed, not predicted. A change is only visible if two scans straddle it, and no account anywhere in this dataset has yet been seen entering the dark state — every dark account was already dark when first observed. There is therefore no basis for forecasting one, and none is offered.
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.930Z.
1 declared capability(ies) did not answer.
| SEP | Declared | Observed | Latency | Detail |
|---|---|---|---|---|
| SEP-6 Programmatic deposit & withdrawal |
declared | not answering | 37ms | fetch failed |
| SEP-10 Web authentication |
declared | answering | 226ms | 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