nTokens Serviços Digitais Ltda
ntokens.com
Identity — verified, not assumed
These accounts are the ones ntokens.com 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.
- GDKL5TOWWA…VLLMT6 — declared
- GCVVC4SL7G…FIKX6P — declared
- GDVKY2GU2D…7DVVSP — declared
SEP-1 resolved successfully at 2026-09-14T15:25:29.776Z.
Settlement record
| Account | State | In | Out | Last seen | History |
|---|---|---|---|---|---|
| GDKL5TOW…VLLMT6 | no activity | 0 | 0 | — | 392 obs |
| GCVVC4SL…FIKX6P | dark | 1 | 0 | 67.4d | 392 obs |
| GDVKY2GU…7DVVSP | slow | 58 | 474 | 20.9d | 389 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.
- GDVKY2GU…7DVVSP went live → slow on 2026-08-28
- GDVKY2GU…7DVVSP went slow → live on 2026-08-24
- GDVKY2GU…7DVVSP went live → slow on 2026-08-24
- GDVKY2GU…7DVVSP went dark → live on 2026-08-19
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:05.962Z.
Every declared and probeable capability answered.
| SEP | Declared | Observed | Latency | Detail |
|---|---|---|---|---|
| SEP-6 Programmatic deposit & withdrawal |
declared | answering | 406ms | 1 depositable, 1 withdrawable asset(s). |
| SEP-24 Hosted deposit & withdrawal |
declared | answering | 202ms | 1 depositable, 1 withdrawable asset(s). |
| SEP-31 Cross-border payments |
declared | answering | 205ms | 1 corridor asset(s) advertised. |
| SEP-12 KYC |
declared | not probeable | — | No public capability document is defined for this SEP. |
| SEP-10 Web authentication |
declared | answering | 106ms | 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