Legal · Discord apps · Developer Portal

Discord intent proof

Effective September 12, 2026 · Last updated September 12, 2026

Index of screenshots, live channels, and in-page mockups that demonstrate why each Nefarious Digital Discord application does or does not need a privileged intent. Built from the published per-bot pages — not from invented tickets.

Discord’s form asks for links to screenshots or videos. Paste the bot’s own proof section, then the live jump URLs below if you have access to those rooms. Do not attach MEE6’s Notion page to any other application.

Questions: Business@nefarious.trading. Matrix: /legal/intents.

01Proof by application

  1. Nefarious nefarious

    Official MEE6 privileged-intent use-case Notion page. Use this URL on the MEE6 Custom Bot form only.

    Do not attach this Notion page to any non-MEE6 application.

    Tutorial · one example

    What this app posts

    Operated by Nefarious Digital. Not financial advice.

    1. MEE6 (skinned as Nefarious) may post a welcome line when a member joins.
    2. Buttons, leveling cards, and automod replies are MEE6 features — this page does not invent them.
    3. Use MEE6’s own privileged-intent proof pack, not a reconstructed Nefarious chat log.

    This application is only a MEE6 Custom Bot skin. Nefarious Digital does not run separate bot code on it. No Nefarious-owned welcome/level message was archived here; MEE6 sends those messages.

    MEE6 Custom Bot output — layout only

    #welcomeLayout from code · no archived source
    NefariousBotLayout from MEE6

    Welcome @member — greeting text is configured in the MEE6 dashboard, not in this repo.

    Standalone HTML mockup: /legal/nefarious/tutorial.html

  2. Nefarious Success nefarious-success

    Image in #success is reposted to X; !scl shows the leaderboard. Needs Message Content.

    Tutorial · one example

    How a success post works

    Operated by Nefarious Digital. Not financial advice.

    1. A member posts an image in #success. Message Content is required to read the attachment and caption.
    2. Nefarious Success uploads that image to @NefariousTrades and replies with a gold embed. No buttons — delete is a 🗑️ reaction.
    3. The reply is from Nefarious Success with a BOT badge.

    Channel 909400273364078612 is the live success room. This repo has no archived member screenshot, so names and the P&L image are omitted. The bot reply layout matches xdiscordsucess.py.

    #successLayout from code · no archived source
    MemberLayout from code

    [member caption, if any]

    [member P&L image — not archived here]

    screenshot.png

    Bot reply after a member image — layout from code

    #successLayout from code · no archived source
    Nefarious SuccessBotLayout from code

    Success posted on Twitter!

    @member earned 1 point. Did you leave any sensitive information? Click 🗑️ to delete the tweet!

    Standalone HTML mockup: /legal/nefarious-success/tutorial.html

  3. Nefarious News nefarious-news

    Outbound news embeds only. No privileged intents. Proof is a posted headline, not a member command.

    Tutorial · one example

    One real example

    Operated by Nefarious Digital. Not financial advice.

    1. There is no member source message. Nefarious News polls public wires (this headline logged from Moomoo).
    2. The bot posts a headline embed into the configured news channel. No buttons.
    3. Output is from Nefarious Newsfeed with a BOT badge. Nefarious Digital operates the bot.

    Posted by Nefarious News — no member source

    #newsReal archived message
    Nefarious NewsfeedBotMar 6, 2026 3:27 AM

    Nefarious Newsfeed

    SPOT SILVER RISES 3% TO $84.64/OZ

    Developed by enickfutures • nefarious.investments

    Standalone HTML mockup: /legal/nefarious-news/tutorial.html

  4. Nefarious Alerts nefarious-alerts

    Alert pings, !stick, and slime/unslime. Message Content + Server Members.

    Tutorial · one example

    How a role ping looks

    This alert bot is free. Operated by Nefarious Digital. Not financial advice.

    1. A watched analyst bot posts in a monitored alert channel.
    2. Nefarious Alerts replies with the configured role ping (`allowed_mentions` roles=True). It does not invent an embed or buttons.
    3. Separate staff commands (`!stick`, slime) are documented on the intents page.

    Nefarious Alerts is free. The ping path is: a watched bot posts, then this bot replies with the alert role mention only — no embed and no buttons. No archived ping pair was extracted into this repo.

    #demon-options-0dteLayout from code · no archived source
    Watched alert botBotLayout from code

    [watched bot’s existing alert — not reconstructed here]

    Nefarious Alerts reply — role ping only

    #demon-options-0dteLayout from code · no archived source
    Nefarious AlertsBotLayout from code

    @alerts

    Standalone HTML mockup: /legal/nefarious-alerts/tutorial.html

  5. Nefarious Backup nefarious-backup

    Webhook mirror plus weekly NAS JSON. Message content is stored off-platform. Members for full roster.

    Tutorial · one example

    How a mirror copy looks

    Operated by Nefarious Digital. Not financial advice.

    1. A member posts in a watched Nefarious channel.
    2. Nefarious Backup mirrors that text (and image URLs) into the private backup guild via webhook.
    3. Weekly snapshots write the same fields to JSON. This is an admin tool, not a public alert product.

    Backup copies live on a private guild and weekly NAS JSON. No public source message is published here. The webhook username is the original author’s display name (App badge), not invented buttons.

    #general-chatLayout from code · no archived source
    MemberLayout from code

    [original message text]

    Backup guild webhook copy — layout from NefariousBackup.py

    #general-chatLayout from code · no archived source
    MemberAppLayout from code

    [original message text]

    Standalone HTML mockup: /legal/nefarious-backup/tutorial.html

  6. Nefarious Widget nefarious-widget

    Voice-channel occupant count for a stream overlay. No privileged intents. Proof is the watched voice room.

    Application id is not in the widget source. Do not invent one.

    Tutorial · one example

    How the overlay works

    Operated by Nefarious Digital. Not financial advice.

    1. There is no member source message. The bot watches one voice channel.
    2. It counts occupants in memory and serves that number as JSON for a stream overlay.
    3. Voice States is a standard intent. Do not request Message Content, Server Members, or Presence.

    Standalone HTML mockup: /legal/nefarious-widget/tutorial.html

  7. Nefarious Congress Tracker nefarious-congress

    Outbound public-filing embeds. No privileged intents.

    Tutorial · one example

    How a filing posts

    Operated by Nefarious Digital. Not financial advice.

    1. There is no member source message. The bot fetches public STOCK Act filings.
    2. It posts one embed (politician, ticker, buy/sell, size, dates). No buttons in the scraper.
    3. Output is from Nefarious Congress Tracker with a BOT badge.

    Channel 1517787034574655518 is the live congress room. This repo has no archived filing body, so the embed below is the field layout from CongressScraper.py — not a reconstructed live PTR.

    Posted by Nefarious Congress Tracker — no member source

    #congress-tradingLayout from code · no archived source
    Nefarious CongressBotLayout from code

    Nefarious Congress

    $TICKER · BUY|SELL · [politician]

    Politician: [name] Type: BUY or SELL Size: [range] Trade date: [date] Filed: [date]

    Leaderboard rank

    [rank]

    Yearly return

    [%]

    Developed by enickfutures • nefarious.investments

    Standalone HTML mockup: /legal/nefarious-congress/tutorial.html

  8. Nefarious Charting nefarious-charting

    !fc BTC (and nf / nfa / nlc) replies with a chart image. Message Content only.

    Tutorial · one example

    One real example

    Operated by Nefarious Digital. Not financial advice.

    1. A member types a prefix command such as `!fc BTC`. Message Content is required to see that text.
    2. Nefarious Charting replies with chart.png. Basic nf/fc replies are the image only — no embed and no buttons.
    3. A live chart.png reply is archived in photon-options (26 Aug 2026). The `!fc BTC` layout matches Nefarious.py.
    #photon-optionsReal archived message
    MemberAug 26, 2026 8:33 PM

    !fc BTC

    Bot reply — chart.png, BOT badge, no buttons

    #photon-optionsReal archived message
    Nefarious ChartingBotAug 26, 2026 8:33 PM
    chart.png — black-theme candlestick (see HTML mockup)

    chart.png

    Jump: https://discord.com/channels/909011353342181426/1493343243998593034/1542270912647401663

    Standalone HTML mockup: /legal/nefarious-charting/chart-command-mockup.html

  9. Nefarious Copytrading nefarious-copytrading

    One signal channel is read over REST. Admin-only. Message Content limited.

    Operator log channel is private. Illustrative signal cards are labeled as such on the intents page.

    Tutorial · one example

    How a signal is logged

    Operated by Nefarious Digital. Not financial advice.

    1. The process polls one Czarfx signal channel over REST and reads the existing NEW TRADE embed.
    2. If operators have connected cTrader, it may place that order on their account.
    3. Nefarious Copytrading posts a COPIED log embed in a private operator channel, with a BOT badge. Admin-only — not a public product.

    Czarfx signal cards exist in channel 1081025463654297640. The card below uses the samples.txt field layout (not a live ticket). No buttons are sent.

    #Czarfx forex signalsLayout from code · no archived source
    CzarfxBotLayout from samples.txt

    NEW TRADE ALERT: 2026-07-06

    Pair : EURAUD Order : SELL NOW Entry : 1.64685 SL : 1.65185 TP1 : 1.64185 TP2 : 1.63185 TP3 : 1.61685 RISK : 0.30%

    Private operator log — posted by Nefarious Copytrading

    #operator-logLayout from code · no archived source
    Nefarious CopytradingBotLayout from samples.txt

    📥 COPIED: EURAUD SELL NOW

    Entry 1.64685 | SL 1.65185 TPs 1.64185 / 1.63185 / 1.61685 Order type: MARKET · Executed via: cTrader (operator account)

    Standalone HTML mockup: /legal/nefarious-copytrading/tutorial.html

  10. Dizu Alerts dizu-alerts

    Dizu’s public alerts are usually a ticker and a fill — for example “Bought SPXL at 297.82” — sometimes with a portfolio card image. The relay’s job is to copy that exact message into destination servers, not to add a stop or a target.

    Tutorial · one example

    One real example

    This alert bot is free. Operated by Nefarious Digital. Not financial advice.

    1. In #dizu-alerts the source post is already from Dizu Alerts: a role ping plus a fill embed (no buttons).
    2. The free Dizu Alerts relay copies that same content and embed into destination servers.
    3. Destination output is posted by Dizu Alerts with a BOT badge. This example had an image and footer, not buttons.
    #dizu-alertsReal archived message
    Dizu AlertsBotAug 17, 2026 3:53 PM

    @dizu-alerts

    Bought SPXL at 297.82 [My Twitter 👀](https://x.com/Dizu_Capital) | [LIVE Portfolio on SavvyTrader!](https://savvytrader.com/MJ_Trade/high-conviction--high-beta?s=MTUyNzMxOjEyNjIw)

    DizuNattsu|Powered by Nefarious.Trading

    [portfolio / fill image from the archived embed]

    image0.jpg

    Destination server — same embed, posted by Dizu Alerts

    #dizu-alertsReal archived message
    Dizu AlertsBotAug 17, 2026 3:53 PM

    @dizu-alerts

    Bought SPXL at 297.82 [My Twitter 👀](https://x.com/Dizu_Capital) | [LIVE Portfolio on SavvyTrader!](https://savvytrader.com/MJ_Trade/high-conviction--high-beta?s=MTUyNzMxOjEyNjIw)

    DizuNattsu|Powered by Nefarious.Trading

    [same archived embed image, forwarded]

    image0.jpg

    Jump: https://discord.com/channels/909011353342181426/1515897463846994101/1538938801261379765

    Standalone HTML mockup: /legal/dizu-alerts/tutorial.html

  11. Slade Alerts slade-alerts · not attested

    Slade Alerts is listed in the Discord Developer Portal as a privileged-intents app and uses the same CryptoCalls relay as the other analyst bots. No slade-alerts channel was in the August 2026 Nefarious channel dump, so this mockup is illustrative of the relay layout — not a reconstructed live ticket.

    No slade-alerts row in Analyst Trade Log/raw/channels.json (dump through August 2026). Operators set the live source in CryptoCalls.

    Tutorial · one example

    How the relay works

    This alert bot is free. Operated by Nefarious Digital. Not financial advice.

    1. Slade Alerts is the same free CryptoCalls-style relay as Dingus and Dizu.
    2. When a source exists, the bot copies that message’s text, embeds, and attachments only — it does not add buttons.
    3. Until a real source message is archived, Discord review should use the Dingus or Dizu tutorial as the layout proof.

    No slade-alerts channel was in the August 2026 Nefarious dump, so there is no archived source message to reconstruct. This page does not invent a ticker, embed, or button. Operators set the live source in CryptoCalls.

    Standalone HTML mockup: /legal/slade-alerts/tutorial.html

  12. Dingus Alerts dingus-alerts

    On 13 July 2026 babajaga2ghz posted a role-ping callout in dingus-alerts: ONDS shares (buy-stop 8.0) and swing options 7 August 10C at 0.09usd. The source had no embed and no buttons. The relay forwards that same text.

    Tutorial · one example

    One real example

    This alert bot is free. Operated by Nefarious Digital. Not financial advice.

    1. Dingus (babajaga2ghz) posts the alert as ordinary text in #dingus-alerts. This example had no embed and no buttons.
    2. Dingus Alerts — a free relay operated by Nefarious Digital — copies that same text into destination servers.
    3. The destination post is from the bot account and shows Discord’s BOT badge. No buttons are added.
    #dingus-alertsReal archived message
    babajaga2ghzJul 13, 2026 3:42 PM

    # @dingus-alerts ONDAS: 1️⃣SHARES: onds buy stop set @ 8.0 I like ondas at this level, if it breaks down again at 7 selling I would consider selling out 2️⃣ SWING OPTIONS: 7th august 10c 0.09usd Let me know if you are trailing any of these by reacting below, I prefer the second play if you want smaller exposure to ondas.

    Destination server — same text, posted by Dingus Alerts

    #dingus-alertsReal archived message
    Dingus AlertsBotJul 13, 2026 3:42 PM

    # @dingus-alerts ONDAS: 1️⃣SHARES: onds buy stop set @ 8.0 I like ondas at this level, if it breaks down again at 7 selling I would consider selling out 2️⃣ SWING OPTIONS: 7th august 10c 0.09usd Let me know if you are trailing any of these by reacting below, I prefer the second play if you want smaller exposure to ondas.

    Jump: https://discord.com/channels/909011353342181426/1524712634778390619/1526252601065083052

    Standalone HTML mockup: /legal/dingus-alerts/tutorial.html

  13. Showtime Alerts showtime-alerts

    Showtime sells premium (cash-secured puts and the occasional covered call). On 24 August 2026 the showtime-options channel posted AAOI 85P 09/18 sell-to-open at 2.82; the next-day buy-to-close at 1.68 was posted as 40% of credit. The relay copies that STO card — text and any thumbnail — to destination servers. It does not add a stop or size your account.

    Tutorial · one example

    One real example

    This alert bot is free. Operated by Nefarious Digital. Not financial advice.

    1. Showtime posts the sell-to-open card as ordinary text in #showtime-options.
    2. Showtime Alerts — a free relay operated by Nefarious Digital — copies that same text into destination servers.
    3. The destination post is from the bot account and shows Discord’s BOT badge. No buttons are added.
    #showtime-optionsReal archived message
    ShowtimeAug 24, 2026

    AAOI 85P 09/18 STO @ 2.82

    Destination server — same text, posted by Showtime Alerts

    #showtime-optionsReal archived message
    Showtime AlertsBotAug 24, 2026

    AAOI 85P 09/18 STO @ 2.82

    Jump: https://discord.com/channels/909011353342181426/1539008052903288853/1541456523895513139

    Standalone HTML mockup: /legal/showtime-alerts/tutorial.html

  14. kly Alerts kly-alerts

    Kly posts stock-swing alerts with a chart stop and a take-profit ladder. On 14 August 2026 the kly-swings channel posted TSLA long at $333, stop $323, targets $345 / $354 / $433 (stated R/R 1:11). The CryptoCalls relay forwards that same text and chart card to destination servers.

    Tutorial · one example

    One real example

    This alert bot is free. Operated by Nefarious Digital. Not financial advice.

    1. Kly posts the swing card as ordinary text in #kly-swings.
    2. kly Alerts — a free relay operated by Nefarious Digital — copies that same text into destination servers.
    3. The destination post is from the bot account and shows Discord’s BOT badge. No buttons are added.
    #kly-swingsReal archived message
    KlyAug 14, 2026

    TSLA long $333 — SL $323 — TP $345 / $354 / $433

    Destination server — same text, posted by kly Alerts

    #kly-swingsReal archived message
    kly AlertsBotAug 14, 2026

    TSLA long $333 — SL $323 — TP $345 / $354 / $433

    Jump: https://discord.com/channels/909011353342181426/1526320262868635868/1537820135895605360

    Standalone HTML mockup: /legal/kly-alerts/tutorial.html

  15. JCAC Alerts jcac-alerts

    JCAC / RadioFX posts forex and gold cards in jcac-futures. On 26 August 2026 the application JCACTrades RadioFX posted XAUUSD SELL NOW (market fill, stop 4682.1). The relay copies that same card — pair, side, stop, and any chart — into destination servers. The source room itself: https://discord.com/channels/909011353342181426/1141525595382108232

    Tutorial · one example

    One real example

    This alert bot is free. Operated by Nefarious Digital. Not financial advice.

    1. JCACTrades RadioFX posts the forex/gold card in #jcac-futures (channel 1141525595382108232).
    2. JCAC Alerts — a free relay operated by Nefarious Digital — copies that same text into destination servers.
    3. The destination post is from the bot account and shows Discord’s BOT badge. No buttons are added.
    #jcac-futuresReal archived message
    JCACTrades RadioFXBotAug 26, 2026

    XAUUSD SELL NOW — market fill — SL 4682.1

    Destination server — same text, posted by JCAC Alerts

    #jcac-futuresReal archived message
    JCAC AlertsBotAug 26, 2026

    XAUUSD SELL NOW — market fill — SL 4682.1

    Jump: https://discord.com/channels/909011353342181426/1141525595382108232/1542155131544674385

    Standalone HTML mockup: /legal/jcac-alerts/tutorial.html

  16. Qiko Alerts qiko-alerts

    Qiko’s public alerts are tight futures scalps (entry / stop / target) plus occasional longer-term crypto ideas and cancels when a fill is missed. On 23 August 2026 the qiko-alerts channel posted “cancelling btc long, missed my fill.” The CryptoCalls relay forwards that same text — and any chart attachment — to destination servers. It does not add a stop or size your account.

    Tutorial · one example

    One real example

    This alert bot is free. Operated by Nefarious Digital. Not financial advice.

    1. Qiko posts the cancel as ordinary text in #qiko-alerts.
    2. Qiko Alerts — a free relay operated by Nefarious Digital — copies that same text into destination servers.
    3. The destination post is from the bot account and shows Discord’s BOT badge. No buttons are added.
    #qiko-alertsReal archived message
    QikoAug 23, 2026

    cancelling btc long, missed my fill

    Destination server — same text, posted by Qiko Alerts

    #qiko-alertsReal archived message
    Qiko AlertsBotAug 23, 2026

    cancelling btc long, missed my fill

    Jump: https://discord.com/channels/909011353342181426/942123328548765706/1541093872392872036

    Standalone HTML mockup: /legal/qiko-alerts/tutorial.html

  17. Johnny Alerts johnny-alerts

    Johnny posts stock and options swing cards — ticker, entry, targets, and often a chart. On 28 January 2026 the johnny-alerts channel posted a $USAR swing: $24 entry at the EMA, $32 take-profit, $22 stop, with a chart image. The CryptoCalls relay forwards that same text and attachment to destination servers. It does not add a size or tell you the trade is suitable.

    Tutorial · one example

    One real example

    This alert bot is free. Operated by Nefarious Digital. Not financial advice.

    1. Johnny posts the swing card as ordinary text in #johnny-alerts.
    2. Johnny Alerts — a free relay operated by Nefarious Digital — copies that same text into destination servers.
    3. The destination post is from the bot account and shows Discord’s BOT badge. No buttons are added.
    #johnny-alertsReal archived message
    JohnnyJan 28, 2026

    $USAR swing — $24 entry at EMA — TP $32 — SL $22

    Destination server — same text, posted by Johnny Alerts

    #johnny-alertsReal archived message
    Johnny AlertsBotJan 28, 2026

    $USAR swing — $24 entry at EMA — TP $32 — SL $22

    Jump: https://discord.com/channels/909011353342181426/1465101799664128177/1466138810537480283

    Standalone HTML mockup: /legal/johnny-alerts/tutorial.html

  18. Drippy Alerts drippy-alerts · not attested

    Drippy Alerts uses the same CryptoCalls relay as the other analyst bots. The drippy-alerts channel is in the Nefarious dump (id 1520964590853165086). The only message in that dump through August 2026 is a subscribe / role instruction, not a reconstructed trade card — so the mockup below shows the relay layout with that attested room text, not a filled ticker ticket.

    drippy-alerts exists in the August 2026 dump, but the only picked message is a /subscribe role note — not a trade alert. Operators still map that source in CryptoCalls.

    Tutorial · one example

    One real example

    This alert bot is free. Operated by Nefarious Digital. Not financial advice.

    1. The dumped source is a subscribe instruction, not a ticker ticket.
    2. Drippy Alerts — a free relay operated by Nefarious Digital — would copy that same text into destination servers.
    3. Until a trade card is archived, this is the attested room text — not an invented fill.

    drippy-alerts exists (1520964590853165086). The only dumped message is a /subscribe role note — not a trade card. The relay still copies source text only; it does not add buttons.

    #drippy-alertsLayout from code · no archived source
    DrippyJun 29, 2026

    do /subscribe with drippy alerts and choose the drippy role

    Destination server — same text, posted by Drippy Alerts

    #drippy-alertsLayout from code · no archived source
    Drippy AlertsBotJun 29, 2026

    do /subscribe with drippy alerts and choose the drippy role

    Jump: https://discord.com/channels/909011353342181426/1520964590853165086/1520966583013474355

    Standalone HTML mockup: /legal/drippy-alerts/tutorial.html

  19. Enick Bot enick-bot · not attested

    No running Discord client in this workspace. Do not invent screenshots.

    Do not invent commands, a client id, or privileged-intent reasons.

    Tutorial · one example

    No invented screenshot

    Operated by Nefarious Digital. Not financial advice.

    1. Do not submit a privileged-intent form for this application until the running client is identified.
    2. These pages are not a MEE6 Custom Bot write-up.
    3. Contact Business@nefarious.trading.

    No running Discord client for this slug was in the workspace. This page does not invent a command, embed, button, or client id.

    Standalone HTML mockup: /legal/enick-bot/tutorial.html

  20. Nefarious Options Levels nefarious-options-levels

    nl / nli prefix commands plus a nightly EOD post. Message Content only.

    Application id is not in bot.ts. Do not invent one. TradingView Pine scripts are not this token’s form proof.

    Tutorial · one example

    How a prefix command looks

    Operated by Nefarious Digital. Not financial advice.

    1. A member with an allowed role types `nl QQQ SPY` (or `nli` plus tickers).
    2. The bot replies with a short fetching status, then edits that message to a compact ticker payload for the TradingView indicator.
    3. No buttons. Message Content is required to see the prefix text.

    Application id is not in bot.ts. This mockup is the nl / nli prefix layout from code — not a reconstructed live levels payload. We do not invent GEX numbers.

    #levelsLayout from code · no archived source
    MemberLayout from code

    nl QQQ SPY

    Bot reply — layout from bot.ts, not a live GEX print

    #levelsLayout from code · no archived source
    Nefarious Options LevelsBotLayout from code

    Fetching end of day levels…

    Standalone HTML mockup: /legal/nefarious-options-levels/tutorial.html

02What not to attach

  • MEE6’s Notion use-case page on any application that is not the Nefarious Custom Bot.
  • A TradingView options-level script as Discord Message Content proof.
  • Invented screenshots, reconstructed tickets, or another bot’s paste answers.
  • Jurisdiction, mailing address, or a designated DMCA agent — we do not publish those.

Also see our Intents matrix, and Discord app legal hub.