Status
OPALE doesn’t have a public status page yet. Until one exists, here’s how to tell if the bot is running and how incidents get communicated.
Quick checks
Section titled “Quick checks”| What | How |
|---|---|
| Bot reachable? | Tap 🏠 Home or send /start in chat. A response within a few seconds means the bot itself is healthy. |
| Trading working? | Tap 🛒 Buy → tap a ticker. If listings load, the WhiteNode integration is up. |
| Deposit confirming? | Verify the transaction on mempool.space. 1 confirmation should credit within 30 minutes. |
| Withdrawal confirming? | Same — check the txid on mempool.space. Stuck txs are usually a Bitcoin network issue, not OPALE. |
How incidents get communicated
Section titled “How incidents get communicated”When something is broken in OPALE itself (not in Bitcoin or in WhiteNode):
- In the bot. During active incidents, OPALE pins a message at the top of the chat with a short summary and ETA.
- On opale.world. Material incidents that affect deposits or trading get a banner.
- In post-mortems. After resolution, longer incidents get a write-up with timeline, root cause, and follow-ups.
Common “is it broken” signals that aren’t OPALE
Section titled “Common “is it broken” signals that aren’t OPALE”- Slow deposit confirmations — Bitcoin network is congested, not an OPALE issue. Deposits credit at 1 confirmation regardless.
- Trade failed with “raced” — listings on WhiteNode are first-broadcast-wins; you lost to another buyer. OPALE retries up to 3 times automatically. See price caps & races.
- Listings showing stale prices — OPALE caches WhiteNode listings and refreshes every ~15 minutes. Wait, or open a fresh quote by tapping 🛒 Buy → ticker.
- Network fees high — Bitcoin-side, not OPALE. Wait for less congested conditions if it’s making small trades unviable.
What’s actually an OPALE incident
Section titled “What’s actually an OPALE incident”- Bot doesn’t respond to any commands or buttons
- Quotes return errors for every token
- Deposits don’t credit even after multiple confirmations
- Receipts never reach
creditedafter the transaction confirmed onchain
If any of those, contact support with the timestamp.
Status page on the roadmap
Section titled “Status page on the roadmap”A public status page (likely at status.opale.world) is planned. Until it exists, treat this section as authoritative.