ng-cn

NGNUSDCCNY

not runnable

Summary

manifest

Source anchor: Nigeria On-Ramp (cNGN/Cowrie-class)
Destination anchor: China RMB Off-Ramp (does not exist yet)
Source asset: USDC
Destination asset: iso4217:CNY
Liveness: not runnable — not runnable
Dest endpoints verified at: never checked

PENDING — no compliant RMB SEP-31 off-ramp exists yet. dest endpoints unfilled.

Liveness warnings

dest has no SEP-31 transfer server — corridor cannot settle. NOT runnable.
fx.quote_source=sep38 but dest exposes no SEP-38 quote server — quotes will fail.
dest has no SEP-12 KYC server — assuming 1:1 delivery with no per-customer KYC.
recovery.timeout_seconds (1200s) does not exceed recovery.reconcile.external_stall_seconds (21600s); the corridor timeout will end pending_external/pending_receiver waits first. Raise timeout_seconds for corridors that need the full external stall budget.

Run a payment on this corridor

Endpoints

manifest

Copied from each anchor's published stellar.toml. A non-empty URL is not evidence an endpoint exists — the date below is.

Field	stellar.toml key	Source anchor	Destination anchor
home_domain	—	example-ng-anchor.invalid	example-cn-anchor.invalid
transfer_server_sep31	DIRECT_PAYMENT_SERVER	not set	not set
web_auth	WEB_AUTH_ENDPOINT	not set	not set
kyc_server	KYC_SERVER	not set	not set
quote_server	ANCHOR_QUOTE_SERVER	not set	not set

Dest endpoints_verified_at: not set (unverified)

FX and settlement

manifest

FX path

NGN → USDC → CNY

Quote source

sep38

Who holds FX risk

sending_anchor

Quote TTL

45s

Bridge asset

USDC

Settlement network

public

Asset issuer

GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN

Recovery policy

manifest

Max retries

Corridor timeout

1200s

Rollback

refund_sender

External stall budget

21600s (default)

Registry attestation

on-chain registry

verify on chain

Attestation for the destination anchor's home domain, example-cn-anchor.invalid. This is the only section sourced from the chain; everything above is what the manifest claims.

Not attested

The registry answered and holds no attestation for example-cn-anchor.invalid. Nobody has probed this anchor on-chain, so there is nothing to show — not a failed probe, and not a passing one.