Discord application · Evidence
Binny Alerts evidence
Effective October 26, 2026 · Last updated October 26, 2026
Inspect this bot’s workflow, identity and supporting records. Each example distinguishes retrieved messages, observed operation and illustrations.
01Workflow and supporting records
Bot identity and authorized use
- Discord bot
- Binny Alerts
1403436512594497671 - Attached analyst / source author
- Binny
- Sender channel
- #binny-sender
1403437120143495303
Application ID verified in the Developer Portal and Discord user lookup. The Discord client identifies the source author as Binny and shows a subsequent send receipt. The full allowlist and the identity of the person who pressed Send were not independently retrieved.
Observed operation · 2026-10-26
The analyst writes an ordinary message without mentioning the bot. Binny Alerts creates an editable preview and offers send controls. Reading that original message requires Message Content in the existing workflow; delivering the output does not. Message-context and slash commands remain alternatives to evaluate.
Actual Discord-client screenshot captured October 25, 2026, showing historical October 8 source, preview and delivery receipt. The receipt reports four successful routes and one failure, not five successful deliveries. Source records were read through the operator’s signed-in Discord tab; the bot collectors lacked channel access. Discord rejected enabling Message Content because this app requires review. On October 26, the signed-in CryptoCalls dashboard independently confirmed application 1403436512594497671, broadcasting enabled and source channel 1403437120143495303. No provider settings were changed; backend code, storage controls and a command fallback were not exposed by the inspected configuration page.
Real Discord source, editable preview and delivery receipt
Inspected October 25, 2026 · Historical capture
- Application
- Binny Alerts / 1403436512594497671
- Source channel
- binny-sender / 1403437120143495303
- Observed workflow
- Ordinary analyst message, editable bot preview, then a sent-with-role-mention receipt
- Reported outcome
- 4 routes successful; 1 failed with Unknown Channel
1. Analyst source
Binny posted a normal message with text and links. No bot mention or slash command is visible in that source.
2. Editable preview
The application replied with a branded embed and controls for send with mention, send without mention, edit title, edit description and edit image.
3. Delivery receipt
A later reply reports routing to four destinations and one failed route. This screenshot does not independently confirm the contents of each destination.
No new message, trade or send interaction was triggered for this capture. Analyst user ID, accepted-click identity, full routing configuration and host storage practices remain unverified. The screenshot alone does not establish that interaction-based alternatives are unsuitable.
02Public evidence and removal
These selected examples are public, including any displayed Discord IDs, messages, timestamps, avatars, media and aggregate operational results. Visitors do not need access to the original channel. Credentials, private trading account details and raw message archives are excluded.
Evidence files and deployment copies have no automatic 30-day expiry. Email Business@nefarious.trading with this bot’s name and the relevant example to request correction or removal. Removal must address active pages, downloads, cached media and retained copies under our control. Evidence is not used to train AI models.