Custom Alerts

Custom Alerts monitor conditions you choose and notify you without placing a trade. Configure them in Synthwav, then receive notifications through your selected browser channels or Synthor in Telegram.

Choose token-specific conditions, favorite-token monitoring, or Market notifications for new tradable tokens, TIP verifications and metadata updates. Repeating ATH/ATL alerts also offer an optional Cooldown Recap.

Create an alert

1. Connect your wallet at Synthwav Trade.
2. Open Custom Alerts using the bell-and-gear icon in the DApp Alerts header, or beside the favorite star in a Pro Mode token details panel.
3. Choose Token or Market. In Token, choose Watch: One token or My Faves.
4. Select the condition and fill in the fields shown for it.
5. Choose when to fire and at least one delivery channel, then select Create alert.

Saving or changing rules may ask you to sign a wallet login message if your session has expired. This is not a trade or an on-chain approval. Reading or receiving alerts does not require signing.

You can also create and manage these same rules in a verified private chat with Synthor. Send /alerts for the button-driven menu, or /newalert to start setup. Choose your settings, review, and confirm; no website visit is needed after wallet linking. The same saved-rule limits apply.

Set a price target from the chart

In Trade, select the token's chart and click the bell-and-gear toolbar button (Set price alert). A price guide follows your pointer. Click or tap a level to open Custom Alerts with One token, the viewed token, Price target, and the selected USD target already filled in. The direction starts as Crosses above for a target at or above the current price, or Crosses below for a lower target. The target remains USD even when the chart displays another currency.

Review the settings and select Create alert to save. Placing a level never saves a rule or executes a trade automatically. Press Esc or click the toolbar button again to cancel. Keyboard users can use the arrow keys to adjust the placement guide and Enter to open the form.

Saved price-target rules appear as bell-and-gear markers and dashed levels on the matching token's chart. Click a marker to edit that exact alert. If levels overlap, choose the rule from the marker's picker. Paused and completed rules remain identifiable; off-screen targets appear when you bring their levels into view. Privacy mode hides saved target levels and markers.

Token: One token

Select a tradable token, then choose a condition:

Buy/sell alerts use indexed trades, not ordinary wallet transfers. A buy matches the token received; a sell matches the token spent. Watched-wallet alerts match the resolved trader, not simply an address appearing in a swap event. Large-trade rules need a known USD value to fire.

Token: My Faves

Choose Watch: My Faves to apply one rule to the connected wallet's server-saved favorite tokens. Available conditions are Percentage move, New ATH, and New ATL.

The rule automatically follows changes to your favorites. Each token has its own baseline, once/repeat state, and cooldown, so one token firing does not block another. Once per token can fire once for each favorite, including favorites added later. One My Faves rule uses one saved-rule slot, not one slot per token.

Newly added favorites establish a baseline before firing. Removed favorites stop being monitored; adding one back starts a new baseline. An empty favorites list leaves the rule waiting. Browser-only favorite changes must synchronize with your wallet before the server can monitor them.

Market

Market watches all relevant tokens, not a selected token or only your favorites. It offers New tradable token, New TIP verified token, and Token metadata update. Each condition uses one saved-rule slot. Market alerts have no cross-token cooldown.

New tradable token

New tradable token watches for future additions to Synthwav's selectable Trade catalog, not every token created on Supra.

Trade and Synthor share the same catalog: Atmos router listings, funded/unpaused WARs pools, and additional Atmos/Hoglet candidates from the existing registry and liquidity snapshot. Candidates missing from the router list require a validated executable quote through the terminal's quote provider. A launch, graduation tag, completion flag, price or old pool record alone never qualifies. Hoglet uses the internal protocol name spikey in existing pool data.

Registry admins can hide an individual token or its verified family from the Trade token selector using the token record's Trade token selector switches. This is a display preference: it does not remove registry/TIP/Portfolio data, block quotes, change existing orders, or change alert membership. Family hiding overrides individual visibility. Restoring visibility does not count as a new listing.

Catalog refreshes share a 30-second cache, in-flight request and Redis refresh lock across serverless instances. Supplemental route proofs are cached for five minutes. At most four background quote attempts run sequentially per 30 seconds, including when registry changes invalidate the catalog. There are no automatic quote retries, candidates rotate across cold runs, and checks stop on rate limiting. A small-input failure can fall back to exact-output for one base unit, avoiding exclusions caused by token precision. Discovery can take multiple refreshes when candidates are queued.

Provider failures preserve last-known display data with a stale flag. Alerts do not initialize or advance their baseline from a partial source catalog. Pending new-listing notifications are checked again before browser/Telegram delivery; unverified notifications queued by the old catalog version are retired without deleting published history. Catalog upgrades preserve all previously seen token identities and seed existing pool/launch candidates before their bounded route probes finish. A delayed first quote for one of those candidates is treated as rediscovery, not a new listing. Later additions can still trigger alerts. Normal delist/relist deduplication continues across upgrades.

Saving records the current catalog as the starting point. Tokens already listed do not trigger an alert. Choose First new token or Each new token. There is no shared cooldown that blocks other new tokens, and a previously seen token does not trigger again merely because it is delisted and relisted.

Discovery depends on catalog updates and successful token resolution. It is not proof of the token's on-chain creation time, safety, or endorsement. After a pause, the rule establishes its current catalog baseline again rather than replaying listings from the paused period.

New TIP verified token

Watches all tokens in TIP, including tokens without a Trade route, for a change from unverified to verified. It uses TIP's existing Authority, administrator, Steward, and active Token Delegate verification rules. Linked Coin/FA representations count as one token family. Tokens already verified at setup are not announced; another edit to an already verified profile does not count as a new verification. Choose First verified token or Each verified token. Verification is not an investment endorsement.

Token metadata update

Watches published TIP names, symbols, logos, metadata URIs, descriptions, websites, social links, and project wallets (including saved SNS names), plus confirmed Floor/WARs descriptions and all custom links. This includes changes made directly on Floor rather than through Synthwav. Price, holder counts, and refresh timestamps do not count as metadata edits. Pending or rejected proposals are not published changes.

Synthor, DApp Alerts, and DApp Popup identify changed fields and their new values. Empty fields are marked Cleared, and removed project wallets are identified by address. Toasts keep their short summary. Large Telegram messages shorten long values or direct you to TIP for additional changes; the DApp retains the detailed rows. Existing hash-only alert baselines begin tracking individual fields on their next successful evaluation, without replaying old updates.

Choose First metadata update or Each metadata update. Existing TIP content is the setup baseline. Floor/WARs checks reuse the on-chain reader and rotate through up to three token families per evaluation tick, shared across wallets. The first successful Floor read establishes that token's baseline without announcing existing content. Large catalogs and failed reads can delay detection; several changes between checks may be reported as one observed change, and a change reversed before a successful check may not be observed. Alerts identify the source and detection time, not an unverified edit timestamp.

Unavailable reads preserve previous baselines, and unchanged content does not repeatedly alert. Saving changes, resuming after a pause, or resuming public availability establishes a fresh baseline rather than replaying changes from the paused period. TIP verification and metadata-update messages use their dedicated Telegram banners with the token logo when available; mixed-condition batches and image failures can remain text-only.

Fire, cooldowns, and new records

Token rules support Once or Repeat. Repeating rules offer cooldowns of 15m, 30m, 1h, 4h, or 24h. Price-target and percentage conditions must leave and re-enter the qualifying condition before another alert; staying above a target does not produce a notification on every check.

ATH and ATL mean records in Synthwav's tracked price history, not an independently verified lifetime record across every venue. Setting an ATH alert while price is already at its recorded high of $1 does not fire. A later price of $1.01 can fire. Retesting the same high does not.

Optional Cooldown Recap

Repeating New ATH and New ATL rules include a Cooldown Recap checkbox, off by default. When enabled, the rule remembers the highest new ATH or lowest new ATL observed during cooldown. At the first eligible check with fresh data after cooldown, one recap can report that record, when it was observed, and the current price—even if price has reversed.

For example, an ATH alert fires at $1.05, observes a new high of $1.10 during its 24-hour cooldown, then price falls to $0.95. With recap enabled, the later recap reports the $1.10 record and the current price. With recap disabled, no delayed notification is sent just because that record occurred during cooldown; another new record must qualify after cooldown.

No new record during cooldown means no recap. A recap does not restart cooldown. If a new live record qualifies at the same check, it includes the recap instead of sending two notifications. Editing or pausing a rule clears pending recaps and establishes a new baseline when monitoring resumes.

Delivery and alert links

Choose one or more delivery channels:

• DApp Toast — a brief title and key line while you use Synthwav
• DApp Alerts — full details in the website's alerts inbox
• DApp Popup — full details in an in-app popup
• Telegram Bot — a private message from Synthor, after wallet verification

Telegram alerts can arrive without Synthwav open. Browser toast and popup checks run every 10 seconds only while the Synthwav tab is visible, and check again when you return. They are not operating-system push notifications for a closed website. The inbox is separate from these transient notifications.

Full alerts include relevant condition details and available actions: Trade [token], View TIP, View Chart, and Manage Alert. Buy/sell alerts can also include View Tx and View Wallet, linking to Suprascan. Telegram uses condition-specific banners with the token logo where available; some combined messages or image failures may be text-only.

Alerts are not instantaneous or guaranteed to arrive at a fixed delay. Server evaluation runs with the one-minute trade-indexing job. Price freshness, transaction resolution, job availability, catalog refreshes, and delivery can add delay. Missing or stale required data does not count as a valid trigger. Alerts never execute a buy or sell automatically.

Manage rules and limits

Expand a rule in My Alerts to edit, pause, resume, or delete it. Use its grip to reorder rules with a mouse or touch, or focus the grip and use the up/down arrow keys. The regular bell in the Custom Alerts header returns to DApp Alerts.

• Standard wallets can save 5 rules; Members can save 20
• Paused and completed rules still count toward the saved-rule limit
• If Membership ends, saved rules remain; the oldest five are eligible by default, or use Keep in free five to choose priorities
• Renewing Membership does not automatically resume rules you manually paused

Rules belong to the connected wallet. Switching wallets changes which rules you manage. Website and Telegram changes apply to the same saved rules.

Troubleshooting

If an alert does not arrive, check that the rule is active, the condition occurred after its baseline, the cooldown permits another trigger, and the intended channel is selected. For Telegram, verify the wallet link and check the private Synthor chat. Unsynchronized favorites, incomplete trade lookup, or missing fresh prices can prevent or delay a trigger.

For bot setup and commands, see Synthor Telegram Bot.