How to use the Blackhat Empire app

Blackhat Empire app 1.3.0 is the Android companion for the alert network. The goal is simple: place the alert, scanner, chart marks, saved-token rules, wallet context, and Academy explanations in one phone workflow. It is information only. The app does not custody funds, does not place orders, and cannot decide for you. It helps you slow down long enough to check the contract, source, and context before you act.

Use this guide as the tour the clip producer can source from. Each section maps to one tutorial topic, and the screenshots on this page show the same app areas: alert feed, scanner and DYOR flow, Academy, modules, and notification controls.

1. Install and first run

Open the Google Play listing from the website or search for Blackhat Empire on Play. Install version 1.3.0, open the app, and allow notifications if you want push alerts. Permission is optional, but it is required for saved-token milestone pushes and inbox history. On first run, confirm that the home screen loads and that the bottom navigation is visible. If Play is unavailable on a compatible Android device, the website keeps the manual APK fallback line for manual updates.

2. Home: track record card

The home view is the fastest way to see how the alert network has behaved recently. Look for the track record card: hit rate, 5x and 10x counts, best alert, and top results. Treat those numbers as history, not a forecast. A useful habit is to compare the card with the Hall of Gains, where peak multiples after our alerts are grouped by time window and chain. The point is to see the record before reading the story around a token.

3. Alerts tab: filters and search

Open Alerts to review live network activity. Filters let you narrow by chain, topic, or text search. Use SOL, BSC, ETH, BASE, and Robinhood-market coverage as separate contexts rather than one mixed feed. Search by ticker only after checking the contract, because names repeat. The alert guide explains families such as MULTIBUY, XTRACK, HYPE, scanner events, rescans, and AI wallet alerts. The label tells you why an item appeared; it is not a recommendation.

4. Token page: price, changes, DYOR on GMGN, Scan, Refresh

Tap an alert to open its token page. Start with chain and contract, then read price, market cap, liquidity, age, and recent changes. Use Refresh when values look stale or when the move is fast. The DYOR button opens the GMGN route so you can inspect the chart and wallet context outside the app. The Scan action brings the contract back into the app scanner so security checks, holders, and market activity stay attached to the same address.

5. Chart: candles with our alert marks

The chart view adds timing. Candles show how price moved around our alert marks, including the first alert and later intervals. Hold to inspect a point instead of guessing from the shape. The useful question is not whether the chart looks exciting; it is where the alert landed, what happened after it, and whether the current area is still close to the evidence you are reading. Chart marks make the alert auditable.

6. Save a token: watchlist and milestone pushes

Tap the star to save a token. Saved tokens move into a watchlist that can send milestone pushes at 2x, 3x, 5x, and 10x since the first Blackhat alert. This is a monitoring tool, not a prompt to act. It helps you separate a result from your timeline mood: the same milestone rule fires whether you are watching the chart or not. If the pushes feel too frequent, change the alert rules or quiet hours.

7. Alert rules: chains, minimum MC, cooldown, quiet hours

Open Alert Rules to decide what reaches your phone. You can choose alert types, chains, minimum market cap, minimum liquidity, cooldown, and quiet hours. Start narrower than you think you need. A smaller, cleaner inbox is easier to review than a loud feed that trains you to ignore everything. Cooldown matters because repeated pushes about one token can create urgency without adding new evidence. Quiet hours protect attention and battery.

8. Notifications inbox: what reached this phone and why

The inbox answers a basic question: what did this phone receive, and why? Each notification should tie back to a rule, chain, topic, or saved-token milestone. When a push feels surprising, open the inbox before opening the chart. Check whether it came from a general alert, a saved-token rule, or a milestone. This makes the push auditable and helps you adjust rules without guessing.

9. Scanner: security checks, holders, market activity

The scanner is for contract-first review. Paste a supported contract and read the available checks, holder distribution, permissions, liquidity context, and market activity. No scanner can prove safety. What it can do is surface reasons to stop, reasons to wait, and fields that are still unknown. If a check is missing, treat it as missing rather than green. Record the unknowns before moving on.

10. Players and wallets: who moved first, DYOR wallet on GMGN

The Players and wallets view helps you see which wallets moved first and whether activity looks concentrated. Do not count every wallet as independent just because the addresses differ. Look for early wallets, repeated patterns, funding relationships, and behavior after the alert. When a wallet needs deeper review, open the GMGN DYOR wallet route from the app and compare what the app shows with the external wallet page.

11. Hall of Gains: 24 h / 7 d by chain

The Hall of Gains gives context to the track record: peak multiple after our alert, grouped by 24 h and 7 d windows and split by chain. Use it to learn which alert families historically led to visible moves and which were noisy. The number is a past peak, not a promise. Pair it with the alert timestamp, liquidity, holder map, and chart marks before deciding whether a current token deserves more research.

12. Why DYOR: facts and marks, the decision is yours

The app shows facts, marks, and explanations. It does not replace judgment. A clean-looking page can miss a new risk; a scary-looking page can include a warning that is already priced in. The right workflow is repeatable: verify the contract, read the alert reason, inspect scanner fields, compare chart marks, review wallets, and write down what remains unknown. If you cannot explain why an alert fired, keep researching or stop. Information first; decision second.