# Introduction
## What is Slate? Slate is **the most predictive alpha feed for social trading ever made**. **Unify your Telegram, Discord, X and tracked wallets** to see tokens before they pump. To build this, we've launched several standalone products: 1. **IPA**: Receive a live feed of alpha extracted from your Telegram chats, with advanced filtering and search commands. 2. **GPA**: Receive a shared, live feed of consolidated alpha from your and your friends' Telegram chats. 3. **Top Telegram Traders**: See a global ranking of traders based on the performance of their calls in Telegram groups. 4. **HL Wallet Tracker**: Get instant Telegram alerts when your tracked HL wallets execute trades. 5. **AI Execution Agent**: Bridge and trade on Hyperliquid, Base and Solana using natural language prompts. # Contact Have questions or want to learn more? DM and FR either @bicep\_pump or @oogway8030 on Discord and mention you're coming from the Slate docs (DMs that don't do this will be ignored). # IPA Slate Information Processing Agent. Starting with Telegram; expansion to Discord, X and on-chain soon. ## User Guide ### Official IPA Link ### Overview The **Slate IPA** is a bot that watches your chosen Telegram groups for calls (like token symbols, contract addresses, or links) and sends you alerts enriched with extra context (e.g., token price, holder distribution, messages around the call, X sentiment). You control which chats to track and how strict the alert rules are. {% embed url="" fullWidth="false" %} ### 1. Security **Your privacy and operational security (opsec) come first. Slate IPA is designed so you never have to trade safety for speed.** 1. **Private, Revocable Telegram Session** * The bot launches *a private session* of your Telegram account solely to read messages in the group you select. It can't post, forward, or join chats on your behalf. * Authenticate through whichever method you trust most: * **Telegram QR Code** - the official flow built by Telegram. * **Open-source authentication script -** run locally or in Google Colab (code provided). * **Phone number + 2-step verification -** Details in Telegram docs under *User Authorization or QR code login.* * **Revoke access instantly:** *Telegram > Settings > Devices* (or my.telegram.org) and terminate the Slate IPA session at any time. * **Built on** [**Telegram's Official Client API**](https://core.telegram.org/#getting-started)**:** Slate IPA uses Telegram's documented client API — the same interface available to third-party clients — so it stays fully within Telegram's Terms of Service. The read-only session is yours alone and can be revoked in two clicks. 2. **Trusted Execution Environment** * The bot is built using a trusted execution environment to ensure secure execution, **protecting sensitive data from unauthorized access or tampering**. 3. **Zero Data Retention** * Messages are streamed, enriched and discarded - **no sensitive data is stored.** 4. **Transparent Team & Proven Backers** * **Backed by** [**Blockchain Capital**](https://www.blockchaincapital.com/) - early investors in Coinbase, Aave, Eigenlayer, CowSwap, Messari, 1inch and more. * See our job posting on Blockchain Capital's website here: . * Fully doxxed team with years of crypto-native development: * Reach out to @shirtlessfounder on Telegram with any questions. We will happily provide team verification. * The Slate Team also has a long history of building in crypto without hiccups. Previously, we built Spice Finance in the NFT Finance vertical. At Spice, we: * Managed $250M in NFT loans, generating \~60% APY during a challenging market. * Ranked Top 10 in points-per-ETH efficiency for automated BLUR farming (Season 2). * Sold out a 555-piece NFT collection in just one hour during the bear market. > **Bottom Line**: Slate IPA only reads the groups you choose, never stores your data, is fully compliant with Telegram's TOS, and can be disconnected in two clicks. *** ### 2. Onboarding 1. **Go to** [**https://t.me/slate\_tracking\_bot**](https://t.me/slate_tracking_bot) 2. **Type** `/start` in a chat with the bot to begin. 3. **Select which onboarding method you'd like to proceed** with and following the subsequent in-chat instructions. 4. **Select the groups** you want to track from a list the bot shows you (it will fetch all your existing Telegram groups/channels). 5. **Pin the Slate IPA chat** so you don't miss out on any notifications. 6. That’s it! You’re now onboarded, and the bot can read messages from the groups you’ve approved. 7. You may see the following notification from Telegram shortly after connecting. Do not fret: this is the Slate IPA. **Click "Yes, it's me" to dismiss.**
> **Notes**: You can revoke this access any time by ending the bot’s session in your Telegram “Active Sessions” (in-app settings). *** ### 3. Essential Commands Below are the main commands you’ll use. Simply type them in your chat with the bot: | **Command** | **Purpose** | | -------------- | ---------------------------------------------------------------------------------------------- | | `/start` | Begin the onboarding flow if you haven’t already, or re-start if stuck. | | `/list` | View a list of all groups you’re currently monitoring. | | `/add` | Opens an interactive menu to add more groups or channels to your tracking. | | `/remove` | Opens a menu to remove any groups from monitoring. | | `/leaderboard` | Shows top-mentioned tokens in the last 24 hours (or a custom time window). | | `/context` | Get a summary of the conversations around a token across all your tracked group chats. | | `/summary` | Get a summary of any kind of conversation in the past X hours. | | `/call` | Label a token you've called as a call in the Slate system | | `/settings` | Access advanced tweaks (user filters, channel enable/disable, thresholds). | | `/request` | Submit feedback or feature requests to the bot developers. | | `/refer` | Refer other users to the Slate IPA. All onboarded referrals will be tracked by the Slate team. | **Usage Examples**: * **Leaderboards**: ```bash /leaderboard ``` or ```bash /leaderboard 12 ``` to see top-mentioned tokens in the last 24 hours (default) or 12 hours (or any look back period you want). * **Context:** ```bash /context [CA/ticker] ``` or ```bash /context [CA/ticker] 2 ``` to see conversation summary for a token in the last 6 hours (default) or 2 hours (or any look back period you want). * **Summary:** ```bash /summary 6 ``` or ```bash /summary 2 [group chat] ``` to see conversation summary of your Telegram or specific group chat over last 6 hours (default) or 2 hours (or any look back period you want). * **Add Groups**: 1. Type `/add`. 2. The bot fetches your untracked groups. 3. Tap each group to select or deselect it. 4. Tap **Done** when you finish. * **Remove Groups**: 1. Type `/remove`. 2. Mark which groups you want to drop from the list. 3. Tap **Done**. *** ### 4. Configuring Your Alerts You can fine-tune which mentions you receive with in-chat menus and commands: 1. **Channel Mentions** * In `/settings` → **Toggle Channel Mentions**, you can disable specific groups if you only want alerts when multiple groups mention a token (confluence) or if you just don’t want direct pings from that group. 2. **Mention Threshold** * `/add_threshold `: Set a minimum mention count. For example, `3` means you only get notified after a token is mentioned 3 times within 24 hours. * `/remove_threshold `: Remove a threshold. 3. **User Filters** * **Whitelist** or **Blacklist** specific users in a selected chat: * `/add_user @username` or `/remove_user @username` after choosing a chat in `/settings`. * **Whitelist** → Only those users trigger alerts. * **Blacklist** → Those users are ignored. *** ### 5. Understanding the Alerts The IPA has several types of alerts in the live notification feed. Here is a breakdown of each of them: **First Confluence:** * The first time **two unique callers across your tracked groups mentions the same token**, you'll receive a notification with the "🥇 **CONFL 🥇"** header alerting you of first confluence. This notification has additional information that details the following: * **\[2c | 2m | 1g] = 2 callers, 2 mentions, 1 group** * Names of the top 3 callers (🗣️) by elo
**Repeat Confluence:** * After the first confluence notification, every time **a new unique caller across your tracked groups mentions the same token**, you'll receive a notification with the "♻️ **CONFL** ♻️" header alerting you of repeat confluence.
**Cabal Alert:** * If a token is mentioned by **3+ unique users and only 1 tracked group**, you'll receive a ntoification with the "⚠️ **CABAL** ⚠️" header alerting you that the mentioned token is a potential cabal token.
*** ### 6. Understanding Caller Elo See the Caller Elo method [here](/products/top-telegram-traders-and-groups). **Relevant Commands:** `/callerleaderboard` - Check global leaderboard (across all IPA users) of the best performing callers visible to the IPA. `/elodistribution` - Better understand the relative distribution of elo scores. `/callerstats [caller username]` - Gives a breakdown of a caller's recent scores. `/call` - Logs a call you've made in a group chat as a call (vs. a scan) to be counted in your elo score. *** ### 7. Troubleshooting & Tips * **Didn’t Receive a Code?**\ Double-check your Telegram client or try `/start` again if you entered a wrong phone number. * **Having a Hard Time Entering the Code?**\ Make sure you're adding a space somewhere between two of the digits in your five digit code from Telegram. Try `/start` again and do so. * **No Alerts?**\ Make sure you have at least one group tracked, and that the group indeed has mentions (like `$XYZ` or `0x...`).\ You might also have set a high **mention threshold**. * **Overwhelmed by Alerts?** * **Toggle** a group off in `/settings`. * **Increase** mention thresholds. * **Add** certain users to a whitelist or blacklist in each chat. *** ### 8. FAQ 1. **How many groups can I track?** * As many as you’d like, though it’s best to keep it reasonable to avoid notification overload. 2. **How do I get rid of the bot entirely?** * Use your in-app Telegram “Active Sessions” to terminate the session. Then you can also delete the bot from your list. # GPA Slate Group Processing Agent ### Overview The **Slate GPA** is a specialized Telegram bot that combines selected users IPAs, finds alpha across all the IPAs and sends a live feed of alerts into a designated "destination" group chat for viewing. #### Why use the GPA? * **Frictionless Alpha Sharing:** Automatically distribute valuable token calls from your IPA’s monitored group chats directly to your closest friends, streamlining alpha sharing effortlessly. * **Comprehensive Coverage:** Gain access to crucial alpha even from group chats you're not personally in—but your friends are—ensuring you never miss valuable opportunities. Your Slate IPA becomes more useful if you and your friends are all tracking separate groups. * **Higher Signal Quality:** All alerts are cross-referenced with a vastly expanded set of chats (from both you and your friends), significantly enhancing the reliability and confidence of notifications. ### 1. Onboarding The GPA is currently a **white-glove service**. You will need to contact the team directly to onboard. 1. Find **group of 5+ friends** and have everyone onboard to the [IPA](/products/ipa). 2. Have each of your friends [add chats to track](https://docs.slate.ceo/products/pages/kvgp8XFngRmjNnlitrkH#id-3.-essential-commands) within their individual IPAs. 3. Decide where (what Telegram channel) you want the GPA to message in. 4. Contact **@shirtlessfounder** on Telegram to request access to the GPA. Include the Telegram handles of all your onboarded friends who wish to participate. 5. Once approved, add @shirtlessfounder to the channel in Step 3. 6. Let us finish up the set up process. ### 2. How the GPA Works **GPA** listens to all of the group chats you and your group are tracking via your IPAs. Whenever someone calls mentions a token ticker (`$XYZ`) or a contract address (`0x...`) in these groups, the bot notes: * **Which user** mentioned it * **Which group** it was mentioned in * **Timestamp** of mention It accumulates mentions in a short-term “mention tracker.” Then: * **Confluence Threshold:** If the same token is mentioned by at least **N** unique callers within a rolling time window (3 hours by default). * **CABAL Alert:** If a token is mentioned by **3+ unique users** but **only in a single group**, it triggers a “CABAL” alert (suggesting coordinated posting in one group). * **Repeat Alerts:** If an alert has already been sent for a token, the bot requires more unique callers than before to trigger a new alert (so it doesn’t spam on the same mention count). ### 3. Understanding the Alerts When the GPA detects a confluence or cabal scenario, it sends a message with a format like: ``` 🥇 CONFL 🥇 [3c | 5m | 2g] on $FOO [MC: $2.4M] 🗣️ Callers: @userA [2], @userB [TBD], ... 🏘️ Groups: ApesChat [3m], DeFiAlpha [2m] 🔎 IPAs: ... 🔗 DS | X | Pump | ... ____________________ ``` [Breaking this down (reference IPA notifications):](https://docs.slate.ceo/products/pages/kvgp8XFngRmjNnlitrkH#id-5.-understanding-the-alerts) * Header**:** `🥇 CONFL 🥇` or `♻️ CONFL ♻️` or `⚠️ CABAL ⚠️` * \[3c | 5m | 2g]**:** * `3c` = 3 unique callers * `5m` = 5 total mentions * `2g` = across 2 groups * $FOO \[MC: $2.4M]**:** The token symbol `$FOO` and approximate market cap if retrieved from DexScreener or other sources. * **🗣️** Callers**:** Lists top 3 callers, plus their caller ELO in brackets. \[2] means that user’s ELO is 2, `[TBD]` means they have no recent track record. * **🏘️** Groups**:** Shows which groups posted about `$FOO`, with mention counts. * **🔎 IPAs: Shows which personal IPA bots or user sessions are also tracking that group.** * **🔗** (Links): Quick links to DexScreener, Twitter, Pump, etc. for deeper investigation. # Top Telegram Traders & Groups **Goal:** Provide you with a number that represents "how practical (good entry and exit) and profitable (high confidence of good, consistent returns) it is to follow this caller or group's token calls." #### What ELO really is: $$ \text{ELO};=; \underbrace{\text{Sortino Ratio}}*{\text{quality per trade}} ;\times; \underbrace{\text{Number of calls}}*{\text{consistency}} $$ Find a more detailed explanation of each component and adjuments made below. For sure reach out to @shirtlessfounder on Telegram if you have any suggestions for improving the system. We're continuously iterating on the ELO calcs. *** ### 1. What gets counted as a “call” A "call" in the system is defined as the first mention of a token per user in a 30 day time window.
RuleReason
First token mention only (per user, per 30 d)Filters out echo-spam and reposts.
*** ### 2. Measuring the performance of a call The performance of a call is dictated by the mcap multiple achieved at the exit mcap (@ T0+3min) from the entry mcap (@ T0). Return per call: $$ r = \frac{mc\_{3m} - mc\_{0}}{mc\_{0}} $$ Some nuances were applied to approximate for call actionability: | Rule | Reason | | ----------------------------------------------- | ------------------------------------------------------------------------------------------- | | **Get entry mcap at time-of-call + 20 seconds** | Gives realistic reaction time after seeing a call notification and entry mcap for followers | | **3-minute holding window** (`mc₀` → `mc₃m`) | Normalizes TP "strategy" across all calls. Average holding time among active trenchers. | *** ### 3. Stat-checks before calculating caller ELO * **Sample-size floor** – A **dynamic threshold of calls** is applied per the look-back window before an ELO is given to the user. * **Lower-bound gate** – The **lower 95 % one-sided confidence limit** of the mean return to cut out lucky moons that are statistically indistinguishable from noise*.* *** ### 4. Calculating the two factors | Ingredient | How we compute it | Why it matters | | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- | | [**Sortino ratio**](https://chatgpt.com/c/681403ef-98f4-800b-ba8b-9bfc074e5353) |

See formula below and explanation here.

Target = 4% returns.

| Rewards upside while punishing only downside. | | **Number of calls (n)** | Count number of first token mentions per lookback window. | More first mentions = higher conviction the ratio is real. | $$ \text{sortino ratio}; = \dfrac{\bar r - \text{target}} {\sqrt{\tfrac{1}{n}\displaystyle\sum\_{r\_i<\text{target}}!\bigl(\text{target}-r\_i\bigr)^2}} $$ ELO is a product of these two factors. A caller with a Sortino of **2.6** over **38** valid calls ends up with an **ELO = 98.8**. *** ### 5. Continuous data refreshing and lookback windows * **Slice size** – ratings are re-evaluated every 12 h slice using only data that existed **before** that slice. * **Lookback windows** – on the leaderboard, we calculate 1d, 7d, 30d and all-time ELOs for each user. Each time period has its own call threshold that's dynamically adjusted according to the dataset. * **Decay** – calls gradually lose weight (half-life ≈ 7 d) so stale edge bleeds away. *** ### 6. Why the method is reliable | Common pitfall | How Caller Elo avoids it | | --------------------- | ----------------------------------------------------------- | | One-hit wonder pumps | Needs a threshold of calls & positive lower-CI. | | Echo-chamber hype | First-mention rule prevents credit for copy-paste alerts. | | Pump and dump callers | Downside in Sortino + optional width-test caps their score. | | Back-test overfitting | Strictly rolling, out-of-sample scoring; no hindsight. | *** #### TL;DR 1. **Clean call data** → first token mention + call actionability adjustments + 3-minute return. 2. **Caller consistency** → callers must achieve a threshold of calls before ELO is assigned. 3. **Risk / downside adjustments** → Sortino ratio calculation. 4. **ELO Score** → Sortino ratio × number of calls. That’s the ELO you see next to every alert and on the global leaderboard. Again, reach out to @shirtlessfounder on Telegram if you have a suggestion on improving the system. # HL Wallet Tracker If you're actively tracking wallets in the Hyperliquid ecosystem and want to be directly notified whenever they take action, you can do so with the Slate Hyperliquid Wallet Tracker Bot. ## Demo (turn on sound) {% embed url="" fullWidth="false" %} ## Requirements 1. List of HL wallets you'd like to track 2. Sign up here: 3. Add list of wallets and labels (see demo above) 4. Tell the Slate team about any specialized notifications you'd like ## Currently Integrated Notifications 1. Label requested wallets to track 2. Whenever a wallet long/short/closes a perp position (limit, market, twap) 3. Whenever a wallet buys/sells a token on spot 4. Whenever a wallet buys/sells anything on hpump 5. Whenever an order is canceled by a wallet 6. Whenever an order is filled by a wallet 7. Whenever any multiple wallets open or exit any specific position (confluence) 8. X min interval summaries of position changes 9. Value thresholds # AI Execution Agent # Overview ## Main View The Main View tab is where you can: 1. Type in the on chain operation you want to generate a transaction pathway for 2. Double check and edit values within the generated transaction pathway and simulation. 3. Execute the on chain operation with one click 4. Abort the on chain operation at any time
## Pending Operations The Pending Operations tab displays a list of your confirmed on chain operations that are on hold, awaiting the fulfillment of certain conditions you've set before they are initiated and carried out. You may cancel pending operations here as well.
## History The History tab displays a list of your successfully executed on chain operations for reference. After successfully executing an operation in the Main View tab, the operation details will be moved to the History tab.
# How It Works ## Slate Wallet Creation ### 1. Sign-Up and Wallet Initialization When you sign up for Slate, we automatically create for you a Slate Wallet with its own wallet address. This wallet is linked to the private passcode you create during the sign-up process. ### 2. Exporting Your Slate Wallet After signing up for Slate, you should: 1. Immediately export your Slate Wallet's private key from the Settings tab. 2. Import this key into your preferred wallet provider (e.g., MetaMask or Rabby). Benefits: * Use your Slate Wallet as a standard Externally Owned Account (EOA). * Easily interact with unsupported applications and other dApps directly (i.e., connecting your Slate Wallet directly to GMX via their Connect Wallet button on their UI). * Simplify wallet funding and transfers through your chosen wallet interface. Doing this enhances the flexibility and usability of your Slate Wallet.
### 3. Importance of Your Privy Passcode It is crucial that you remember your Privy passcode. This code acts as a recovery and identification key for your embedded wallet. If you lose this code, it will be **IMPOSSIBLE** to recover your embedded wallet and the assets within.
## Slate Wallet In Action ### 1. On-Chain Execution It's best to think of your Slate Wallet as your "execution wallet." This wallet is what Slate uses to execute your requested on-chain operations on your behalf. All of the "from" addresses for your transactions will be the address of your Slate Wallet. Make sure that you fund your wallet with the appropriate tokens and on the appropriate chain before you attempt to execute your prompt. ### 2. Automations (Conditions) Slate allows you to remain full self-custody of your funds AND execute condition-based prompts (that can't be done anywhere else) like the following: * "long doge with 100 usdc on gmx on arbitrum when funding rate goes above -0.13%" * "buy usdc with 0.5 eth on arbitrum when eth price goes above $3700" * "stake 2.5 eth on lido on ethereum next friday at 5pm utc" * "swap 1000 $magic for $eth when $magic market cap falls below $50M" * "when gas is sub 40, bridge 0.5 eth worth of dai from ethereum to arbitrum" * etc. That said, Slate requires you to do the following to execute your conditional prompts while AFK: #### Desktop Instructions: 1. Keep your Slate browser tab open. 2. Prevent your laptop/desktop from entering sleep mode (black screen). * Set your device's "Turn display off on battery when inactive" (or equivalent) setting to "never."
#### Mobile Instructions: 1. Download the Slate Progressive Web App (PWA) on your mobile device. 2. Log in with your Slate account. 3. Keep the Slate PWA running in the background. 4. This method eliminates the need to keep your desktop open and running.
By following these steps for either desktop or mobile, you'll be ready to execute your conditional prompts as intended. ### 3. Funding Because your Slate Wallet is your execution wallet, it needs to be properly funded with the appropriate tokens on the appropriate chain prior to executing your prompt. To do so, just go to the funds sidenav, click Connected Wallet and click on the token you want to transfer to move it over to your Slate Wallet. ### 4. Handling Gas Your Slate Wallet is responsible for covering gas costs. Make sure your wallet has sufficient funds to carry out your desired operations by transferring the necessary native tokens on the appropriate chain to your Slate Wallet. ## Slate Wallet Custody & Security Slate uses Privy's embedded wallet architecture. This allows for your Slate Wallet to be **fully self-custodial** while allowing Slate to execute prompts on your behalf. For comprehensive details on this, read more [here](https://docs.privy.io/guide/frontend/embedded/overview). Below, we will walk you through the basics. ### 1. Private Key Splitting [Shamir’s Secret Sharing](https://en.wikipedia.org/wiki/Shamir%27s_secret_sharing) is used to split your Slate Wallet's private key into three distinct shares and reassemble them when it comes time to execute your prompt. These are the three shares your private key are split into: * Device Share: Stored securely in your browser’s local storage and is retrieved when the Slate browser tab is opened. * Auth Share: Stored on Privy’s server and is retrieved when you authenticate (i.e., sign the message in your wallet, log in with socials, etc.) and log into the Slate application. * Recovery Share: Stored encrypted on Privy's server and is decrypted and retrieved only when you've entered your password to log into the Slate application. Importantly, neither Privy nor Slate store the password which unlocks your Recovery Share, meaning neither they nor we can decrypt the Recovery Share on our own. This ensures that if either Privy or Slate's systems were compromised, the attacker would be unable to access your Recovery Share because the decryption key (your password) is not within Privy nor Slate’s purview. ### 2. Private Key Shares In Action #### Reconstruction & Execution To reconstruct the private key, at least two of the three shares are needed. When prompts are executed on your behalf, Privy/Slate will securely reconstruct your Slate Wallet's private key (meaning neither system will see the reconstructed private key) using your Device Share and Auth Share. In practice, this means neither Privy nor Slate can perform transactions on behalf of your Slate Wallet unless you've authenticated, entered your password and have your Slate application browser tab open ([hence the requirements for executing conditional prompts above](#id-2.-automations-conditions)). This ensures that the private key itself is never fully exposed nor stored in one place, maintaining a non-custodial system while allowing Slate to still execute prompts for you at the point of execution. #### Re-creation The system that holds your Device Share in your browser's local storage naturally expires after some time to maintain security (think: similar to how Google randomly logs you out of your account after a while and prompts you to re-enter your password to log in again). You may wonder: "what happens to the Device Share when this happens or my browser's local storage gets cleared by some other means?" When you log in, Privy will use your Auth Share and Recovery Share to re-create Device Share and you'll be good to go with the necessary three shares. This is also what happens when you log into Slate from a different device (like a different computer, browser, phone, etc.) using the same password to access the same Slate Wallet. ## Connected Wallet ### 1. Easy Fund Onboarding and Off-boarding To use Slate, you must connect an external wallet to the dApp. Once connected, you can use this connected wallet to easily fund the Slate Wallet through Slate's UI. ### 2. Switching Connected Wallets Once you're on the Slate UI, you're able to switch your connected wallet by simply switching wallets in your wallet provider (i.e., MM or Rabby). After switching to a new connected wallet, you may use this new wallet to log into Slate moving forward. # Prompting Guide Below, you will find best practices for prompting Slate and lists of example prompts for your reference. ## Prompting Best Practices Slate will continuously get better at understanding prompts, regardless of how they're worded, over time. However, for now, it's wise to follow certain guidelines to increase the chances that Slate correctly interprets your prompt and creates the right transaction pathway for you. Let's review these guidelines. ### 1. Phrase prompts as executable commands Slate's primary function is executing transactions. Thus, when you prompt Slate, phrase your prompts as commands and begin each command with the action word. Currently, it cannot handle research-related queries. However, this capability is planned for future implementation. > Bad Prompt: "what is gas on ethereum right now?" > > Good Prompt: "swap all of my $BLUR to wETH on ethereum" ### 2. Do not have conversations with Slate The AI is non-conversational in it's current design. Each prompt is independent of the last. Slate does not remember your prompt history as context for the next. > Bad Prompt: "no, I meant to wETH" > > Good Prompt: "swap 0.5 wETH to USDC on arbitrum" ### 3. Provide all transaction details in your prompt Check the input checklist above the prompt bar after typing an action word. Include all listed details to avoid inaccuracies.

Checklist that will appear above your prompt bar after you type in an action word.

> Bad Prompt: "swap for usdc on ethereum" > > Good Prompt: "swap 0.01 eth for usdc on ethereum" ### 4. Describe complex intents step-by-step Slate works by combining simple transactions to perform complex tasks. For better results, clearly describe each step of what you want to do in your prompt. As time goes on, Slate will get better at understanding and executing more complicated intents. > Bad Prompt: "Deposit into the safest yield on ETH Mainnet" > > Good Prompt: "Deposit 0.05 ETH into Aave" ### 5. Do not include mentions of the sender Keep in mind that all actions executed by Slate are carried out using your embedded wallet. Therefore, when prompting, there's no need to mention the sender, as the sender will always be your embedded wallet address. > Bad Prompt: "Use 0xA1C7656EC7ab88b098defB751B7401B5f6d8976F to transfer 0.1 ETH to 0xF4E9A55D2D88485D3C30B3176F6F8524ABF42E76" > > Good Prompt: "Transfer 0.1 ETH to 0xF4E9A55D2D88485D3C30B3176F6F8524ABF42E76" ### 6. Be as specific as possible For the best chance of accurate interpretation, it's important to use clear and precise language when specifying actions, protocols, tokens, and chains for your transactions. Try to avoid slang, abbreviations, and CT jargon whenever possible. > Bad Prompt: "Buy 0.01 ETH, bridge to arb and send it to my external wallet" > > Good Prompt: "Buy 0.01 ETH with USDC, bridge it to Arbitrum and transfer it to 0xF4E9A55D2D88485D3C30B3176F6F8524ABF42E76" ### 7. Avoid adding superfluous information Adding extra information to your prompt will only reduce interpretation accuracy. > Bad Prompt: "get out of my staked OHM and into stETH, bridge everything to arbitrum. optimize for price execution" > > Good Prompt: "get out of my staked OHM and into stETH, bridge everything to arbitrum" ### 8. Stay within scope You can find a list of integrated protocol-action-chain combinations that you can prompt in the sidenav on the left. To ensure that your prompt can be successfully executed, make sure that what you're trying to do is possible within Slate's current integration set. Keep in mind that this set of integrations will be continuously expanded over time. > Bad Prompt: "withdraw everything from JonesDAO on arbitrum" > > Good Prompt: "withdraw 0.001 eth from the weth pool from compound on base"
## Example Prompts Below are \[non-exhaustive] lists of prompts that have been successfully executed. Use these lists as guides to understand the format for effective prompts and see the range of operations that Slate can perform. ### Example Regular Operations 1. "claim my aerodrome rewards on base" 2. "sell eth for 1000 usdt and lend it on aave on ethereum", 3. "bridge 50 dai from arbitrum to base and deposit it into the aerodrome dai-usdc pool on base" 4. "sell usdc for 1.3 weth on uniswap and deposit it into aave on ethereum" 5. "bridge all of my tokens on linea to ethereum" 6. "stake 100 of my $pls on plutus on arbitrum" 7. "buy 710 usdt with eth and lend it on aave on ethereum" 8. "withdraw all of my usdc from the camelot eth-usdc pool on arbitrum and bridge it to base" 9. "close link position on gmx on arbitrum" 10. "on arbitrum, swap all of my of my fxs to frax, lend it on lodestar, and borrow 0.005 usdt from lodestar" 11. "withdraw all of the wavax i have in the gmx wavax-usdc pool on avalanche" 12. "long doge with 5x leverage with 140 usdc on gmx on arbitrum" 13. "sell all my $grail on arbitrum for usdc.e" ### Example Conditional Operations 1. "when gas is sub 40, bridge 0.5 eth worth of dai from ethereum to arbitrum" 2. "swap $170 worth of eth for xrp on ethereum when xrp market cap goes below $3.75 billion" 3. "bridge all of my eth from ethereum to arbitrum tomorrow at this time" 4. "lend 115 dai on aave on ethereum when dai supply apy goes above 8% and gas is sub 40" 5. "swap 0.65 eth for usdc on ethereum when eth goes above $2500" 6. "swap 110 eth for usdc on ethereum in 12 hours" 7. "claim pending aerodrome staking rewards on base every 45 days" # Memecoining Guide Welcome to the Slate guide on trading memecoins using our AI-powered DeFi automation tool. This guide will help you understand the basics of swapping tokens, introduce you to relevant automations, and provide example strategies to optimize your trading experience (NFA). Reference this guide whenever you find yourself stuck on how to phrase a memecoining prompt on Slate. ## Basics on Swapping "Swapping" is the fundamental action being taken for trading in low-cap or meme tokens. Usually, it'll involve swapping from a stable or native token into the target memecoin or swapping out to take profit. Swapping occurs when certain specific conditions hit, such as price changes or PnL changes. With Slate, you can execute swaps using simple natural language commands, making the process more efficient and you more powerful on-chain. ### How to Swap Tokens with Slate To perform a basic swap using Slate, you can use commands like: * **"Buy $NEIRO with 0.01 ETH on Ethereum"** * **"Swap 2 ETH for $BABYDOGE on Ethereum"** These commands instruct Slate to execute the swap on the specified blockchain network using the specified amounts and tokens ### Understanding the Command Structure When swapping tokens with Slate, you'll want to include at least: * **Action**: Buy, sell, or swap. * **Amount**: Specify the amount in tokens or fiat currency. * **Token**: The cryptocurrency you want to trade. * **Network**: The blockchain network (i.e., Ethereum, Binance Smart Chain). **Examples**: * **"Buy $1,000 worth of $SHIB on Ethereum"** * **"Swap 1000 $SHIB to $USDC on Ethereum"** * **"Sell all of my $SHIB to $ETH on EThereum"** This command tells Slate to swap into or out of $SHIB tokens to a specific token on the Ethereum network. If an input or output token isn't specified in your prompt, as in the first example above, Slate will infer you want to use a stable or native token to perform the swap (whichever is available). ## Relevant Automations Slate offers various automations to help you manage your trades effectively. These automations allow you to set conditions under which certain actions will be executed automatically. **\*\*\* ⛔️WARNING⛔️: Be sure to follow through** [**these instructions**](https://docs.slate.ceo/products/ai-execution-agent/pages/ecmBgBCKajd7LLgGo099#id-2.-automations-conditions) **to make sure your automations execute successfully. \*\*\*** ### 🎯 Price-Based Automations * **Profit Targets**: Sell tokens when they reach a certain profit level. * *Example*: **"Buy $NEIRO with 0.01 ETH on Ethereum and sell when its price hits 2x"** * *Example*: **"Sell all of my $NEIRO when the price goes above $0.01"** * **Trailing Stop Loss**: Sell tokens if the price dips by a specified percentage. * *Example*: **"Buy $NEIRO with 0.01 ETH on Ethereum and sell it if its price dips 50%"** For relative targets (i.e., "2x" or "dips 50%"), Slate will calculate the target price of the token using the current price at the time of confirmation. ### 🎯 Gas Fee Automations * **Gas Price Conditions**: Execute trades when gas fees are favorable. * *Example*: **"Buy $NEIRO with 0.01 ETH on Ethereum when gas is sub 40 gwei"** Gas fee automations are good for when Mainnet gets congested and you want to save costs, for example. ### 🎯 Market Cap and FDV Automations * **Market Capitalization Triggers**: Sell tokens when market cap reaches a certain value. * *Example*: **"Sell half of my $NEIRO when its market cap goes above $350,000,000"** * **Fully Diluted Valuation (FDV) Conditions**: Act based on FDV metrics. * *Example*: **"Sell a quarter of my $NEIRO when its FDV goes above $350,000,000"** Market Cap and FDV automations may be useful especially for tracking new tokens and their growth. ### 🎯 Time-Based Automations * **Scheduled Trades**: Execute trades at a specific time. * *Example*: **"Buy $1,000 worth of $SATO at 12:01 PM EST"** * **Repeating Actions**: Set up trades to repeat over a period. * *Example*: **"Sell 10% of my $BLUR every 4 hours for the next day"** These time-based automations are good for when you have to go to bed or need to step out to buy groceries and want to execute a transaction. Otherwise, you can also use this automation to "snipe" new tokens. Let's say you know the liquidity pool for a new token is going to be launched at 12 PM EST, you can set a time-based automation to buy the token at 12:01 PM EST, let's say. ### 🎯 Balance Automations * **Balance Value Conditions**: Act when your holdings reach a certain value. * *Example*: **"Sell all of my $NEIRO when my $NEIRO balance reaches $30,000"** * *Example:* **"Every time my $PEPE holdings increase by $500 in value, swap that amount to USDC"** These automations are good for managing your portfolio profits at large, depending on what your intended strategy is with your memecoin buys. Take profits, anon. ### 🎯 PnL Automations * **Profit and Loss Targets**: Sell when you reach a specific profit amount. * *Example*: **"Sell all of my $NEIRO when I 2x on it"** These automations are good for managing your memecoin profits and portfolio at large, depending on what your intended strategy is with your memecoin buys. ## Strategies and Pathways to Implement Using Slate, you can implement various trading strategies to supercharge your memecoining efforts. NFA. ### 🎛️ Strategy 1: Cross-chain Position Rotation **Command**: * **"Swap half of my $DEGEN on Base for $NEIRO on Ethereum"** **Explanation**: Slate's especially quick at automating your position rotations. If you know you want to exit a memecoin position and enter into another one with the profits, Slate will calculate the best pathway for you, optimizing for price execution. ### 🛟 Strategy 2: Price Execution Optimization **Command**: * **"Buy $1000 worth of 0xA12ba41e071c7b7fa4ebcfb62df5f45f6fa853ee on Ethereum"** **Explanation**: Slate aggregates all relevant exchanges on EVM. If you know a contract address or ticker for a memecoin that you'd like to purchase, doing so on Slate will ensure that you get the best price execution on-chain without needing to do all the research and comparisons yourself. ### 📉 Strategy 3: Buying the Dip **Command**: * **"Buy $1,000 worth of $SHIB on Ethereum when its price drops by 5% within 24 hours"** **Explanation**: This strategy involves purchasing tokens when the price decreases by a certain percentage, allowing you to buy at a lower price with the expectation of future gains. ### 💵 Strategy 4: Scheduled DCA Position Exiting **Command**: * **"Sell $500 worth of $SHIB every day at 10:00 AM for the next 7 days"** **Explanation**: This strategy involves investing a fixed amount of money at regular intervals, reducing the impact of volatility by averaging out the purchase price over time. It is a disciplined approach to accumulating tokens over a period. ### 💰 Strategy 5: Profit Taking **Command**: * **"Sell all my $DOGE holdings if the price increases by 10% in the next hour"** **Explanation**: This strategy helps lock in profits by selling when the token price reaches a specified gain within a set time frame. ### 💸 Strategy 6: Incremental Profit Taking **Command**: * **"Sell 20% of my $NEIRO holdings every time its price increases by 10%"** **Explanation**: Gradually taking profits as the token price rises helps you secure gains while still keeping a portion of your holdings invested for potential further appreciation. ### ⛽️ Strategy 7: Gas Fee Optimization **Command**: * **"Swap 2 ETH for $BABYDOGE on Ethereum when gas fees are below 25 gwei and $BABYDOGE price dips by 5%"** **Explanation**: By combining gas fee conditions with price triggers, you can minimize transaction costs and buy tokens at a favorable price. ### ⚖️ Strategy 8: Value-Based Rebalancing **Command**: * **"Every time my $PEPE holdings increase by $500 in value, swap that amount to USDC"** **Explanation**: This approach allows you to secure profits incrementally by converting gains into a stablecoin, thus reducing exposure to volatility. ### ⏰ Strategy 9: Time-Based Entry for New Token Launches **Command**: * **"Buy $1,000 worth of $SATO at 12:01 PM EST"** **Explanation**: Participating in new token launches promptly can be critical. This strategy allows you to schedule a purchase at the exact time a new token becomes available, ensuring you don't miss out on potential early gains. ## Conclusion Slate empowers you to execute complex DeFi trading strategies using simple natural language commands. By utilizing the various automations and strategies outlined in this guide, you can enhance your trading efficiency and effectiveness. # Integrations Below, you will find comprehensive lists of integrated protocols, actions, conditions and chains for your reference. ## Integration Lists Below, you'll find comprehensive lists for the protocols, actions, conditions, tokens and chains that are currently integrated into Slate. These lists will continuously expand as we ship along our roadmap. > Prompts which include protocols, actions, conditions, tokens and chains NOT LISTED BELOW are NOT SUPPORTED by Slate and WILL NOT execute. ### Actions 1. Borrow 2. Bridge 3. Claim 4. Close 5. Deposit 6. Lend 7. Lock 8. Long 9. Repay 10. Short 11. Stake 12. Swap 13. Transfer 14. Unlock 15. Unstake 16. Vote 17. Withdraw ### Protocols 1. 0x 2. 1inch 3. Aave 4. Across 5. Aerodrome 6. Ambient 7. Axelar 8. Balancer 9. Bungee 10. Camelot 11. Compound 12. Cowswap 13. Curve 14. DeBridge 15. Dolomite 16. Eigenlayer 17. EtherFi 18. GMX 19. Hashflow 20. Hop 21. Juice 22. Jumper 23. KelpDAO 24. Kyberswap 25. Leetswap 26. Lido 27. LiFi 28. Llamazip 29. Lodestar 30. Matcha 31. Odos 32. OpenOcean 33. Orbiter 34. PancakeSwap 35. ParaSwap 36. Pendle 37. Plutus 38. Socket 39. Squid 40. Stargate 41. Sushiswap 42. Swell 43. Synapse 44. SyncSwap 45. Thena 46. Thruster 47. TraderJoe 48. Uniswap 49. Velodrome 50. Ethena 51. Renzo ### Tokens Prompt Slate using the name, symbol OR contract address of the token. For names or symbols, Slate currently conforms to [Coin Market Cap](https://coinmarketcap.com/) and [Coin Gecko](https://www.coingecko.com/). ### Chains 1. Arbitrum 2. Avalanche 3. Base 4. Blast 5. Binance 6. Ethereum 7. Linea 8. Mode 9. Mantle 10. Optimism 11. Polygon ### Conditions 1. Time * Target (e.g., "... at 5 PM EST today") * Timer (e.g., "... in 5 mins") * Repeating (e.g., "... every Friday at 5 PM EST") - note: currently, repeating conditions will repeat indefinitely until you cancel them on our UI 2. Gas * Range (e.g., "... when gas is below 30") 3. Balance * Range (e.g., "... when my BLUR balance increases 20%") 4. Price * Range (e.g., "... when ETH goes above $2700") 5. Health Factor * Range (e.g., "... when health factor of my Lodestar position falls under 1.2") 6. LTV * Range (e.g., "... when LTV of my Frax position falls on Lodestar goes above 40") 7. Market Cap * Range (e.g., "... when $DEGEN goes above $400,000,000 market cap) 8. FDV * Range (e.g., "... when $DEGEN goes above $400,000,000 FDV) 9. APY * Range (e.g., "... when the usdt supply apy goes above 7%") # Fee Structure (Not Final) ## Introduction This document outlines the detailed fee structure for our new product, aiming to provide users with clear information on how fees are determined based on their interactions within the platform. *** ## Fee Structure Overview ### **Volume-Based Fees** * **Principle:** Fees are calculated based on transaction volume and vary according to the type of action performed. * **Calculation Method:** Each action within the platform has an associated fee, calculated as a percentage of the transaction's volume. ### Special Consideration for Dependent Transactions * **Dependency Detection:** Our system intelligently detects dependent transactions. For example, if you swap $1000 USDC for 0.5 ETH and then bridge the 0.5 ETH, the prompt's volume is considered as $1000 (or 0.5 ETH) without double counting. * **Accurate Fee Application:** This ensures users are charged fairly, avoiding overcharges for interconnected transaction sequences. ### **Fee Dictionary** Here is the fee table, where percentages indicate the fee as a percentage of the transaction volume: * **Regular Actions:** Actions like 'transfer', 'swap', 'bridge', etc., each have a designated fee. * 0.00%: transfer, deposit, withdraw, vote * 0.35%: swap, bridge, claim, borrow, lend, repay, stake, unstake, long, short, lock, unlock * **Conditional Actions:** 'condition', 'time', 'gas' – Fees are only incurred if these actions are executed (e.g., fees for a limit order condition apply only when the order is executed). * 0.25%: gas conditions * 1.00%: all other conditions * **Multi-action Transactions:** The numbers '2', '3', '4', '5' represent the quantity of actions combined in a transaction. There is no fee category for a single action ('1'), and any number of actions beyond five falls under the '5' fee category. * Example: A prompt involving three actions will incur the '3' fee. A prompt with eight actions will be charged under the '5' fee category. | Number of Actions | Fee Percentage | | ----------------- | -------------- | | 2 | 0.50% | | 3 | 0.75% | | 4 | 1.00% | | 5+ | 1.25% | *** ## Fee Accrual and Payment System ### **Accruing Fees** * **Method:** Fees are accrued to your account rather than being charged immediately. * **Summation:** These accrued fees are requested to be paid once they far exceed the gas cost of transfer. ### **Payment of Fees** * **Currency:** Fees are requested in the native (gas) token of the chain with the highest native balance. * **Transparency:** A scheduled fee transaction is displayed for your approval before any transaction. *** ## Conclusion Our fee structure is crafted to be transparent, fair, and easy to understand, allowing users to use our product with confidence and clarity. For further inquiries or detailed explanations, our support team is readily available to assist. # Discord Channel Token Tracker Bot If you've joined many, noisy Discord channels and want notifications for ticker or CA mentions across them, you can do so with the Discord Channel Token Tracker Bot. ## Requirements 1. ***Slate logs in to your Discord account*** 1. Tell Slate team your Discord account login credentials (email/phone number & password) 2. Tell Slate team any MFA information 2. Tell the Slate team what servers you want to be notified about 3. Tell the Slate team about any specialized notifications you'd like ## Currently Integrated Notifications Any of these notifications can be toggled on or off or modified by request. 1. Whenever a token is mentioned in any requested server 2. Whenever a token is mentioned in any specific channel of the server (default if you add a server is all channels) 3. Whenever a token is mentioned in a server/channel by specific users only 4. Whenever a token is mentioned between 2 different servers/channels 5. Whenever a token is mentioned multiple times in a certain timeframe 6. Whenever a token under X mcap is mentioned ## Demo
# TG+Discord Confluence Bot If you're a trench warrior spread thin across multiple channels on Telegram and Discord for sourcing alpha, you may be interested in our Telegram/Discord Confluence Bot. This bot will notify you whenever confluence is found between your Telegram group chats and Discord servers. ## Requirements 1. ***Onboard to the*** [***TG Group Chat Token Tracker Bot***](https://app.gitbook.com/o/90Oc6AqGuShvNu7mabsJ/s/fB7XroTA2gc0nP99UyUl/~/changes/90/notifications/tg-group-chat-token-tracker-bot) ***and the*** [***Discord Channel Token Tracker Bot***](https://app.gitbook.com/o/90Oc6AqGuShvNu7mabsJ/s/fB7XroTA2gc0nP99UyUl/~/changes/90/notifications/discord-channel-token-tracker-bot)***.*** 2. Tell the Slate team what confluence threshold you want applied (e.g., X mentions of a token over Y minutes) ## Currently Integrated Notifications Any of these notifications can be toggled on or off or modified by request. 1. Whenever a token is mentioned between your TG group chats and Discord servers within a certain timeframe ## Demo