LINK.IO LTD.

Identity — verified, not assumed

These accounts are the ones ngnc.online 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.

• GASBV6W7GG…QGXZY6 — declared
• GCQLPBWOQ5…74HVSQ — declared

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

Settlement record

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.

Trend

2 state change(s) observed across this anchor's accounts, 1 of them to a weaker state.

• GCQLPBWO…74HVSQ went slow → live on 2026-09-14
• GCQLPBWO…74HVSQ went live → slow on 2026-09-11

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.445Z. 2 declared capability(ies) did not answer.

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/ngnc.online/profile.json