Back to Engineering Notes

Mooncoin Electrum Server Online on Port 50002

infrastructure 2026-02-20

Context

We deployed a public-facing mooncoin electrum server endpoint and opened port 50002 for encrypted client connectivity tests. This is a core infrastructure step for scaling query access beyond direct full-node RPC and for supporting future mooncoin wallet and mooncoin dev integrations.

Objective

  • Validate baseline Electrum protocol compatibility for Mooncoin chain data access.
  • Establish an operational boundary between full-node consensus operations and query-layer traffic.
  • Prepare reliable backend primitives for browser wallet and bot-facing services.

Technical Approach

Infrastructure shape:

  • Mooncoin full node as canonical chain source
  • Electrum index/query layer on top
  • TLS endpoint exposed on 50002

Representative validation commands:

nc -vz <electrum-host> 50002
openssl s_client -connect <electrum-host>:50002 -servername <electrum-host>

Health verification from backend side:

mooncoin-cli getblockchaininfo
mooncoin-cli getnetworkinfo

What We Implemented / Verified

Verified

  • External connectivity to 50002 is reachable.
  • TLS handshake succeeds for the exposed endpoint.
  • Basic query-path responsiveness is available for iterative client tests.

Partially Verified

  • Extended session stability under burst query traffic is still being measured.
  • Long-duration behavior during node reorg or index catch-up is not fully characterized.

Not Yet Verified

  • Public hardening profile for adversarial traffic is not finalized.
  • Formal SLO/SLA definitions for response latency are not yet established.

Risks and Open Questions

  • What rate-limit policy keeps service useful without enabling abuse?
  • Should anonymous query depth be capped by method type?
  • How should index lag be exposed to clients to prevent stale reads?

Failure boundary example:

  • If backend index lag is not surfaced and clients assume tip-level freshness, wallet balance and confirmation UX can become misleading even when consensus is healthy.

Next Steps

  • Add metrics for query latency, connection churn, and backend lag.
  • Define method-level rate limits and error taxonomy.
  • Run staged load tests before broader public promotion.