QUICKTXN / DOCUMENTATION

Troubleshooting and support

Keep the transaction hash and response details. Leave credentials out of the report.

Common problems

Chain discovery is unexpected

Stop submission. Confirm the exact assigned hostname and chain ID; do not override Host headers or connect directly to an origin IP.

The request returns 401 or 403

Check X-Api-Key, product, submission enablement, and chain grants. A valid key for another product or chain is insufficient.

Fee discovery returns 503

For explicitly untipped accounts this can mean no tip gate. Otherwise confirm readiness and fee configuration with support. Do not infer free submission.

I have a hash but no receipt

Read the matching chain RPC. A null receipt is not proof of failure. Poll with a deadline and check nonce state before any replacement.

I see already known or nonce too low

Look up the original hash and sender nonce. Duplicate network submissions can happen after timeout or upstream retry.

The endpoint is slow from my region

Measure connection setup separately from reused-connection response latency and receipt timing. More edge regions do not eliminate the upstream distance.

Contact support

Use your existing account contact or Hello Moon Discord. Share the UTC timestamp, chain ID, endpoint hostname, HTTP status, redacted response, and public transaction hash when appropriate. Use your established private support channel for private transaction information. Never include X-Api-Key values, signing keys, seed phrases, or signed transaction bytes in a public report.

Changelog

7 September 2026 — Expansion documentation. Added the nine-region footprint, explicit Columbus/Oregon migration, managed onboarding, and the new QuickTxn credential model. Planned locations are not announced as live. Existing customer instructions remain authoritative until migration is confirmed.