Member01
Register, log in, acknowledge risk
Users can register, log in, see subscription state, and accept the current risk version. Inactive or unacknowledged users cannot create usable rules.
Docs
Docs
These docs explain the current manual-activation workflow for users and administrators of the spot-arbitrage opportunity alert service.
No auto-trading, no custody, and no profitability promise.
ArbPingDocs
01Member onboarding
02Telegram binding
03Alert rules
04Notification logs
ArbPing docs for activation, Telegram binding, alert rules, notification logs, manual admin subscriptions, and troubleshooting.
Member
Shortest path from registration to alert
Follow these steps to move from registration to an alert-ready member state. Each result remains visible in the member portal.
Telegram02
Bind and verify a target
The main flow uses binding codes and deep links. Manual Chat ID entry is only for support troubleshooting. Unverified targets cannot receive formal alerts.
Rules03
Save personalized alert conditions
All supported symbols are selected by default. Members can paste bulk lists, restrict exchanges, and set minimum estimated value, cooldown, and quiet hours.
Logs04
Confirm delivery records
After delivery processing, members and support can inspect notification records, attempt status, and failure reasons.
Member onboarding
Members register or log in, confirm subscription state, bind a private Telegram target, and create alert rules. Alert rules affect distribution only; they do not change the central scanning strategy.
Telegram binding
Private chat targets are supported first. A target must be verified and enabled before it can receive alerts.
Alert rules
Rules can filter by estimated value, spread, symbol, buy exchange, sell exchange, cooldown, and quiet hours. Rules do not bypass global route safety state.
Notification logs
Members and admins should be able to inspect delivery status, attempt counts, and failure reasons. Duplicate processing of the same opportunity must not create duplicate deliveries.
Troubleshooting
If no alerts arrive, check subscription status, target verification, rule thresholds, symbol or exchange filters, and whether real sending is enabled.