ZEAM LIMITED
zeam.money
Identity — verified, not assumed
These accounts are the ones zeam.money 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.
- GAKTLPC4ZV…5U6XPR — declared
- GCZLKDDJ5F…WBF2DC — declared
- GA5ZXXHHXX…DEJCFL — declared
- GAROH4EV3W…TJBB3U — declared
- GD3MMNHD5U…QAGOLD — declared
- GAIVVKIZV2…BCKPZX — declared
- GCXZTK7XDP…RVCP42 — declared
- GDZL62FHKS…QVHW7X — declared
- GCGJOW22JX…KAPXPQ — declared
- GA37M2LDWC…6HCVLI — declared
- GAT63G6FIN…AGBTCZ — declared
- GAM5BKSKTH…NKEURZ — declared
- GDZBAWPUGA…OYZARZ — declared
- GCTG4YT2ZT…FDGBPZ — declared
- GAP5YLVKIS…RKGON5 — declared
SEP-1 resolved successfully at 2026-09-14T15:25:29.776Z.
Settlement record
| Account | State | In | Out | Last seen | History |
|---|---|---|---|---|---|
| GAKTLPC4…5U6XPR | dark | 2 | 11 | 83.1d | 56 obs |
| GCZLKDDJ…WBF2DC | dark | 12 | 12 | 83.1d | 56 obs |
| GA5ZXXHH…DEJCFL | slow | 58 | 62 | 10.2d | 56 obs |
| GAROH4EV…TJBB3U | slow | 38 | 20 | 10.2d | 56 obs |
| GD3MMNHD…QAGOLD | dark | 0 | 2 | 383.1d | 56 obs |
| GAIVVKIZ…BCKPZX | dark | 2 | 2 | 357.7d | 56 obs |
| GCXZTK7X…RVCP42 | dark | 11 | 3 | 157.2d | 56 obs |
| GDZL62FH…QVHW7X | dark | 2 | 0 | 185.0d | 56 obs |
| GCGJOW22…KAPXPQ | dark | 2 | 0 | 185.0d | 56 obs |
| GA37M2LD…6HCVLI | dark | 2 | 0 | 185.0d | 56 obs |
| GAT63G6F…AGBTCZ | dark | 3 | 5 | 108.3d | 56 obs |
| GAM5BKSK…NKEURZ | dark | 6 | 11 | 66.3d | 56 obs |
| GDZBAWPU…OYZARZ | dark | 2 | 3 | 416.2d | 56 obs |
| GCTG4YT2…FDGBPZ | slow | 2 | 5 | 11.1d | 56 obs |
| GAP5YLVK…RKGON5 | dark | 1 | 1 | 217.3d | 56 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
3 state change(s) observed across this anchor's accounts, 3 of them to a weaker state.
- GA5ZXXHH…DEJCFL went live → slow on 2026-09-07
- GAROH4EV…TJBB3U went live → slow on 2026-09-07
- GCTG4YT2…FDGBPZ went live → slow on 2026-09-06
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:07.718Z.
Every declared and probeable capability answered.
| SEP | Declared | Observed | Latency | Detail |
|---|---|---|---|---|
| SEP-24 Hosted deposit & withdrawal |
declared | answering | 297ms | 2 depositable, 2 withdrawable asset(s). |
| SEP-31 Cross-border payments |
declared | answering | 274ms | 1 corridor asset(s) advertised. |
| SEP-38 Firm quotes |
declared | answering | 97ms | Quote server answered. |
| SEP-12 KYC |
declared | not probeable | — | No public capability document is defined for this SEP. |
| SEP-10 Web authentication |
declared | answering | 95ms | 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