← All anchors

MYKOBO

mykobo.co

2declared accounts
0settling now
2dark > 30 days
865inbound indexed
963outbound indexed

Identity — verified, not assumed

These accounts are the ones mykobo.co 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.

SEP-1 resolved successfully at 2026-09-14T15:25:29.776Z.

Settlement record

AccountStateInOutLast seenHistory
GAQRF3UG…DXZ7NM dark 4 31 34.4d 380 obs
GCY37QZU…EUTKBD dark 861 932 34.4d 379 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, 4 of them to a weaker state.

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:04.970Z. 4 declared capability(ies) did not answer.

SEPDeclaredObservedLatencyDetail
SEP-6
Programmatic deposit & withdrawal
declared not answering 233ms fetch failed
SEP-24
Hosted deposit & withdrawal
declared not answering 40ms fetch failed
SEP-31
Cross-border payments
declared not answering 29ms fetch failed
SEP-12
KYC
declared not probeable No public capability document is defined for this SEP.
SEP-10
Web authentication
declared not answering 10ms fetch failed

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:

/api/v1/anchors/mykobo.co/profile.json

Scan of 2026-09-14T15:25:29.776Z · verified against stellar.expert · methodology · dispute a figure on this page