Skip to main content
Find answers to frequently asked questions below.
There are a few common reasons for this:
  1. Server Not Activated: A server Owner or Administrator must activate the server in the Shuriken Terminal before message processing can begin. Check the connection status in the Alpha Platform settings.
  2. Bot Permissions: Ensure the Shuriken Bot has the necessary View Channel and Read Message History permissions for the specific channels you want to monitor.
  3. User Access: The system respects Discord’s permission model. You will only see messages from channels that you personally have access to.
This is usually due to one of the signal’s conditions or safety features:
  1. Conditions Not Met: The mentioned token may not have met your specific criteria for market cap, liquidity, or age.
  2. 24-Hour Deduplication: To prevent spam, a signal will only fire once per token every 24 hours by default. If the same token was alerted on recently, it will be skipped.
  3. Max Fires Reached: Check if your signal has a Max Fires limit. If it has reached its limit, it will be automatically disabled.
  4. Signal Disabled: Verify that the signal is enabled in your signal list.
Security is our top priority.
  • Official Bots: When using the recommended Official Shuriken Bots, the system operates within the standard, secure permission models of Discord and Telegram. The bot only has access to what you explicitly grant it.
  • Personal Accounts (BYO Alpha): When you connect a personal account, we encrypt your access token and use it only to process messages for signal evaluation. However, this method gives our system broad access to your account’s messages. We strongly recommend using a dedicated “burner” account for this purpose.
Token metadata is fetched in near real-time. When a signal evaluation is triggered, we fetch the latest on-chain data for the mentioned token. There may be a few seconds of latency, but the data is generally very current.