Ultra Capital LLC
ultracapital.xyz
Identity — verified, not assumed
These accounts are the ones ultracapital.xyz 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.
- GAVBS6SXMR…VTQWWY — declared
- GCBPMB2VK3…SWTTBO — declared
- GADFXROGGR…BMCODA — declared
- GD7G6G56JH…U5XS33 — declared
- GA3UK3JHOY…JIVOAJ — declared
- GDGTVWSM4M…ZNTTFF — declared
- GDYQNEF2UW…DERQFD — declared
- GARDNV3Q7Y…DL5T55 — declared
- GBUVRNH4RW…E7L6NW — declared
- GDVKAVKZDK…2GQOOF — declared
- GANESLOXBZ…6766GV — declared
- GBFXOHVAS4…MGSOCC — declared
- GDPJALI4AZ…5O2MZM — declared
SEP-1 resolved successfully at 2026-09-14T15:25:29.776Z.
Settlement record
| Account | State | In | Out | Last seen | History |
|---|---|---|---|---|---|
| GAVBS6SX…VTQWWY | slow | 1 | 72 | 25.1d | 57 obs |
| GCBPMB2V…SWTTBO | slow | 0 | 3 | 23.7d | 57 obs |
| GADFXROG…BMCODA | live | 1 | 206 | 2.0d | 57 obs |
| GD7G6G56…U5XS33 | dark | 0 | 17 | 53.8d | 57 obs |
| GA3UK3JH…JIVOAJ | dark | 0 | 0 | 67.4d | 57 obs |
| GDGTVWSM…ZNTTFF | live | 30 | 10 | 30.2h | 57 obs |
| GDYQNEF2…DERQFD | live | 9 | 1 | 30.2h | 57 obs |
| GARDNV3Q…DL5T55 | live | 136 | 4 | 30.2h | 57 obs |
| GBUVRNH4…E7L6NW | live | 9 | 0 | 30.2h | 57 obs |
| GDVKAVKZ…2GQOOF | live | 407 | 54 | 30.2h | 57 obs |
| GANESLOX…6766GV | live | 6 | 6970 | 0.0h | 57 obs |
| GBFXOHVA…MGSOCC | live | 37 | 1 | 30.2h | 57 obs |
| GDPJALI4…5O2MZM | live | 10 | 2 | 30.2h | 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
11 state change(s) observed across this anchor's accounts, 3 of them to a weaker state.
- GDGTVWSM…ZNTTFF went slow → live on 2026-09-13
- GDYQNEF2…DERQFD went dark → live on 2026-09-13
- GARDNV3Q…DL5T55 went slow → live on 2026-09-13
- GBUVRNH4…E7L6NW went dark → live on 2026-09-13
- GDVKAVKZ…2GQOOF went slow → live on 2026-09-13
- GDPJALI4…5O2MZM went slow → live on 2026-09-13
- GBFXOHVA…MGSOCC went slow → live on 2026-09-12
- GADFXROG…BMCODA went slow → live on 2026-09-07
- GBUVRNH4…E7L6NW went slow → dark on 2026-09-07
- GDGTVWSM…ZNTTFF went live → slow on 2026-09-05
- GDPJALI4…5O2MZM went live → slow on 2026-09-05
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.793Z.
Every declared and probeable capability answered.
| SEP | Declared | Observed | Latency | Detail |
|---|---|---|---|---|
| SEP-6 Programmatic deposit & withdrawal |
declared | answering | 179ms | 2 depositable, 2 withdrawable asset(s). |
| SEP-24 Hosted deposit & withdrawal |
declared | answering | 463ms | 6 depositable, 6 withdrawable asset(s). |
| SEP-10 Web authentication |
declared | answering | 28ms | 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