WORK SAMPLE·Edward Tay·BD qualification tool

Anchor Readiness Check

Qualify a company as a Stellar anchor before you book the meeting. It runs SEP-1 discovery on the domain, then calls every endpoint that company declares to see which ones actually answer, then verifies their issued assets onchain against Horizon: issuer account, domain reciprocity, compliance flags, trustlines and supply. Declared and working are different things, and the gap between them is the conversation.

ⓘ Independent tool built by Edward Tay for a job application. Not affiliated with, endorsed by, or operated by the Stellar Development Foundation. Read-only public data: SEP-1 files, the endpoints those files advertise, and the Horizon public API. No keys, no wallet, nothing stored.
Check a domain
Live Stellar ecosystem centre.io (USDC) stellar.org lobstr.co ultrastellar.com vibrantapp.com mykobo.co anclap.com
APAC qualification set kenanga.com.my marketnode.com coins.ph airwallex.com xendit.co hashkey.com jpyc.co.jp bigpay.com.my
Scan a list of domains

One domain per line. This is the artifact the job actually needs: a whole market qualified in one pass and sorted by how far along each company already is. Four at a time, to stay polite to the hosts.

What this actually checks
StepRequest madeWhat it proves
SEP-1 discoveryGET https://<domain>/.well-known/stellar.tomlWhether the company has published anything on Stellar at all, who they say they are, and which services they claim.
Endpoint livenessGET <TRANSFER_SERVER>/info, <TRANSFER_SERVER_SEP0024>/info, <DIRECT_PAYMENT_SERVER>/info, <ANCHOR_QUOTE_SERVER>/info, <KYC_SERVER>/customer, <WEB_AUTH_ENDPOINT>Whether the declared services are running. A stale file pointing at dead endpoints is common, and it changes the pitch completely.
Advertised capabilityParses each /info payloadWhich assets they actually ramp and in which direction, whether cross-border receive (SEP-31) is configured, and whether firm quotes (SEP-38) exist.
Onchain verificationGET horizon.stellar.org/accounts/<issuer>That the issuing account exists, and that its home_domain points back at this domain. A one-way claim is not an issuer.
Compliance postureReads the issuer account flagsauth_required, auth_revocable, auth_immutable, auth_clawback_enabled: the controls a regulated issuer needs, visible onchain.
Real distributionGET horizon.stellar.org/assets?asset_code=&asset_issuer=Trustlines and circulating supply. The honest size of an issued asset, rather than the number in the announcement.
Limits, stated plainly
  • A missing SEP-1 file proves nothing was published at that domain. A company can run a Stellar integration under another domain or through a provider. Check before writing anyone off.
  • A live /info proves the service answers, not that it settles volume.
  • Some hosts block datacentre traffic. That shows as unreachable, and is labelled unreachable rather than absent.
  • Horizon reflects mainnet only. Testnet work is invisible here.
  • Trustlines count accounts that opted in, which is an upper bound on real users.
Why a business development person wants this

The first meeting is the scarce resource. Walking in knowing that a prospect declared SEP-24 two years ago and the endpoint has been dead since is worth more than any deck. It converts a generic partnership pitch into one specific question: what stalled, and who owned it. The batch tab does the same thing for an entire market in one pass, which is how you decide where to spend a quarter.

Live network state
…latest ledger
…operations in that ledger
…base fee, stroops
…USDC trustlines on Stellar

Read live from Horizon, the public Stellar API.