Documentation & FAQ

Learn how to use Bitty Bot!

General Information

  • All commands are case insensitive, UPPER or lower case is fine.
  • Only 1 Bitty Bot command per comment/message. If I find multiple, only the first counts.
  • I recommend your Bitty Bot command be on its own line, but I will still try my best to find it.
  • Position and order of parameters is important, don't swap them around!
  • All dates and times are in the UTC timezone.
  • All numbers support K and M suffixes. $50k = $50,000. 2M = 2,000,000.
  • All prices support a ATH keyword that can be used instead of the price for predictions, notifications, limit trades & commands, stop losses, take profits, etc. Example: !bitty_bot predict >ATH 3 days
  • [param] brackets mean a parameter is optional.
  • You can direct message u/Bitty_Bot (message, NOT Reddit Chat) your command if you do not want to post it in r/BitcoinMarkets
  • Feedback is always welcome, send Bitty Bot a message if you need help or have a suggestion!

Frequent Questions

Bitty Bot cannot currently see comment edits (though, we might be able to fix this is the future). When you post a comment in a supported subreddit, Bitty Bot sees it and checks for a valid command and then never reads that comment again. Please post a new comment with the appropriate command to trigger your notification, prediction, or paper trade.

Great question! You can do that in the r/Bitty_Bot Testing Area. Any commands posted in r/Bitty_Bot will trigger a response from the bot, but will not actually save a notification, prediction, or paper trade. Perfect for testing to make sure you have the format right!

Sure! Just send Bitty Bot a message and he will be happy to help fix it. Note: Please send a support message as quickly as possible, Bitty Bot may refuse to fix mistakes that seem like they are from regret instead of an honest typo!

Bitty Bot gets price information from Coinbase Pro and only Coinbase Pro.

Originally, Bitty Bot checked the price via the Coinbase API roughly twice a second. However, this was not fast enough to catch quick wicks during times of high volatility. Bitty Bot now listens to the Coinbase websocket and checks every single trade on Coinbase against all price triggers. Additionally Bitty Bot will check the high and low candle prices against all price triggers as a backup. This ensures that absolutely no price triggers are missed.

Yes! As of Jan 28 2024, Bitty Bot accepts sats via the Lightning Network so users can pay to reload their Paper Trading Cash Balance. Your cash balance is allowed to go negative and still allow you to trade, but you are limited to a max trade size of $5k + Leverage. For example, 10,000 sats (worth $) will reload your balance $100,000.

For fairness, you can only reload if your balance is below $100k and you cannot reload your balance past the original $100k. (For example, if your balance is -$200k you can reload a max of $300k to get your balance back to $100k)

Bitty Bot is about giving back and adding fun to the r/BitcoinMarkets community, not making a profit. All sats paid will be put into a Prize Pool for use in future trading tournaments.

Learn More About Balance Reloads

The Bitty Bot Prize Pool is the amount of sats users have paid Bitty Bot for things like balance reloads. All sats in the Prize Pool will be used for future trading tournaments and other prizes. Bitty Bot does not keep any sats for itself.

Dates and Times

Both notify and predict modes below have options to add dates. Below are options u/Bitty_Bot can understand. Other formats may result in your date not being recognized and being ignored.

Date Option Notification Result Prediction Result
Tuesday Next Tuesday 00:00:00 UTC Next Tuesday 23:59:59 UTC
Jan 1 2024 2024-01-01 00:00:00 UTC 2024-01-01 23:59:59 UTC
3 Feb 2024 2024-02-03 00:00:00 UTC 2024-02-03 23:59:59 UTC
August 15th, 2024 2024-08-15 00:00:00 UTC 2024-08-15 23:59:59 UTC
3 Feb 2024 6:00 2024-02-03 06:00:00 UTC 2024-02-03 06:00:00 UTC
18:00 Today 18:00:00 UTC Today 18:00:00 UTC
30 minutes Exactly 30 minutes later Exactly 30 minutes later
2 hours Exactly 2 hours later Exactly 2 hours later
3 days Exactly 3 days later Exactly 3 days later
2 weeks Exactly 2 weeks later Exactly 2 weeks later
6 months Exactly 6 months later Exactly 6 months later
2 years Exactly 2 years later Exactly 2 years later
never N/A Special: see Prediction Section Below
  • Relative dates add time to the current time. For example, "1 day" will be exactly 24 hours later, "3 days" will be exactly 72 hours later, etc.
  • Bitty Bot can understand weekdays. For example "Monday" will parse to the NEXT Monday UTC time. Weekdays will never parse to the current day, if today is Monday, a day 7 days from now will be used.
  • If not using relative dates, notifications will default to the start of the day, 00:00:00 UTC.
  • Predictions will default to the end of the day, 23:59:59 UTC.

Price Command

!bitty_bot price - Prints the current price from Coinbase Pro

Notify Command

Notifies the user when the price crosses above or below a certain price point, or at a certain date or time from now. Does not enter any entries in the leaderboards, just triggers a notification.

!bitty_bot notify [>|<price] [date | time from now] [u/NotifyUser7302KJ u/NotifyUser463IA] ["message"]

    !bitty_bot notify [>|<price] [date | time from now] [u/NotifyUser7302KJ u/NotifyUser463IA]

  • [>|<price] Optional:
    • > to be notified when higher than price
    • < to be notified when lower than price
  • [date | time from now] Optional: See table above for date or time from now options.
  • [notify list of users] Optional: List of users to also notify when the notification is triggered. List of users separated by spaces.
  • ["message"] Optional: Message to be included in the notification trigger. Message MUST be surrounded by double quotes like: "message"

Note: At least one of price or date/time from now is required. If both are specified, the notification will fire for whichever comes first.

!bitty_bot notify >$50,000 5 days - will notify the user when the Bitcoin price rises above $50,000 or in 5 days, whichever comes first.

!bitty_bot notify Jan 10 2024 - will notify the user with the Bitcoin price on January 10th, 2024 00:00:00 UTC

!bitty_bot notify <40000 - will notify the user if the Bitcoin price falls below $40,000

!bitty_bot notify >100000 u/NotifyUser7302KJ u/NotifyUser463IA - will notify the user if the Bitcoin rises above $100,000 and will also notify the following 2 users: u/NotifyUser7302KJ u/NotifyUser463IA

!bitty_bot notify >100000 u/NotifyUser7302KJ u/NotifyUser463IA "it hit 100k!" - will notify the user if the Bitcoin rises above $100,000 and will also notify the following 2 users: u/NotifyUser7302KJ u/NotifyUser463IA. In the response when the notification is triggered "it hit 100k!" will be included

Predict Command

Allows users to make predictions of price direction with optional date or time expirations. Predictions are tracked on a leaderboard.

Users can place predictions with a date or time from now. By default if the prediction is correct any time BEFORE the specified date or time, the prediction is marked as correct. However users can optionally put an = in front of the date or time to indicate they want the prediction decided at exactly that date and time and NOT before. See examples below.

Note: To prevent abuse (thanks u/_TROLL), if including a date, predictions must be at least 60 minutes in the future. Prediction prices must also be at least 1% away from the current price.

!bitty_bot predict [!]>|<price [[=]date | time from now] [u/user to set prediction for] [notify u/NotifyUser7302KJ u/NotifyUser463IA]

!bitty_bot predict <>price-range [[=]date | time from now] [u/user to set prediction for] [notify u/NotifyUser7302KJ u/NotifyUser463IA]

    !bitty_bot predict [!]>|<price [[=]date | time from now] [u/user to set prediction for] [notify u/NotifyUser7302KJ u/NotifyUser463IA]

  • [!]>|<price (adding ! in front of > or < inverts your prediction) Required:
    • > to predict BTC will trade higher than price
    • < to predict BTC will trade lower than price
    • !> to predict BTC will NOT trade higher than price
    • !< to predict BTC will NOT trade lower than price

    • !bitty_bot predict <> price-range [[=]date | time from now] [u/user to set prediction for] [notify u/NotifyUser7302KJ u/NotifyUser463IA]

  • <> price-range Required:
    • <> to predict BTC will stay within the specified price-range
    • price-range must be formatted with a "-" between 2 prices, with no spaces. Example: $40k-$50k
  • [[=]date | time from now | never] Optional: See table above for date or time from now options. The "never" option inverts your prediction. For example, <40,000 never would mean the prediction is wrong if the price ever drops to $39,999.99 or below. ("never" cannot be used with the NOT operator ! above) Note: Never predictions are never marked as correct. They stay "open" until proven wrong, if ever.
    • = before a date or time from now will prevent the prediction price from being checked until exactly the date or time specified (see examples below)
  • [u/user to set prediction for] Optional: Used to tell the bot to set the prediction for another user. Useful if a user makes a prediction but does not call the bot. If not specified the prediction will be set for the user that calls the bot.
  • [notify list of users] Optional: List of users to also notify when the prediction is triggered. Useful as a reminder if prediction is in the distant future. "notify" keyword followed by list of users separated by spaces.

!bitty_bot predict >50,000 - Prediction that BTC will trade over $50,000 with no expiration (defaults to 30 days) is entered for the user that writes the command.

!bitty_bot predict <$30,371.82 Jan 1 2024 - Prediction that BTC will trade below $30,371.82 any time BEFORE 2024-01-01 23:59:59 UTC is entered for the user that writes the command.

!bitty_bot predict <$30,371.82 =Jan 1 2024 - Prediction that BTC will be below $30,371.82 at exactly 2024-01-01 23:59:59 UTC is entered for the user that writes the command.

!bitty_bot predict <30,000 never notify u/NotifyUser7302KJ - Prediction that BTC will never trade below $30,000. $29,999.99 or below causes prediction to trigger and be wrong. The user u/NotifyUser7302KJ will also be notified when triggered.

!bitty_bot predict >101123 2 months u/TestUser827AZ - Prediction that BTC will trade above $101,123 any time BEFORE the date exactly 2 months from now is entered for the user u/TestUser827AZ no matter who writes the command. This should only be used if u/TestUser827AZ wrote a comment making that prediction.

!bitty_bot predict >101123 =2 months u/TestUser827AZ - Prediction that BTC will be above $101,123 exactly 2 months from now is entered for the user u/TestUser827AZ no matter who writes the command. This should only be used if u/TestUser827AZ wrote a comment making that prediction.

!bitty_bot predict <9600 19 Oct 2025 u/TestUser827AZ notify u/NotifyUser7302KJ u/NotifyUser463IA - Prediction that BTC will trade below $9,600 any time BEFORE 2025-10-19 23:59:59 UTC is entered for the user u/TestUser827AZ and the following 2 users will also be notified when the prediction hits or expires: u/NotifyUser7302KJ u/NotifyUser463IA

!bitty_bot predict <9600 =19 Oct 2025 u/TestUser827AZ notify u/NotifyUser7302KJ u/NotifyUser463IA - Prediction that BTC will be below $9,600 at exactly 2025-10-19 23:59:59 UTC is entered for the user u/TestUser827AZ and the following 2 users will also be notified when the prediction hits or expires: u/NotifyUser7302KJ u/NotifyUser463IA

!bitty_bot predict >$61000 7 days notify u/NotifyUser7302KJ u/NotifyUser463IA - Prediction that BTC will trade above $61,000 any time BEFORE exactly 7 days from now is entered for the user that writes the command and the following 2 users will also be notified when the prediction hits or expires: u/NotifyUser7302KJ u/NotifyUser463IA

!bitty_bot predict !>$45000 Dec 31 2023 - Prediction that BTC will NOT trade above $45,000 any time BEFORE 2023-12-31 23:59:59 UTC. Prediction will be right if it expires on the date, or will be wrong if the price is ever above $45,000

!bitty_bot predict !<$25,000 Apr 1 2024 u/TestUser827AZ - Prediction that BTC will NOT trade below $25,000 any time BEFORE 2024-04-01 23:59:59 UTC is assigned to u/TestUser827AZ. Prediction will be right if it expires on the date, or will be wrong if the price is ever below $25,000

!bitty_bot predict <> $25,000-$35,000 Apr 1 2024 u/TestUser827AZ - Prediction that BTC will trade between $25k and $35k UNTIL 2024-04-01 23:59:59 UTC is assigned to u/TestUser827AZ. Prediction will be right if it expires on the date, or will be wrong if the price is ever below $25,000 or above $35,000

!bitty_bot predict <> $25,000-$35,000 =Apr 1 2024 u/TestUser827AZ - Prediction that BTC will be between $25k and $35k at exactly 2024-04-01 23:59:59 UTC is assigned to u/TestUser827AZ. Prediction will be right if it expires on the date, or will be wrong if the price is ever below $25,000 or above $35,000

Paper Trading

Paper trading allows users to make fake BTC trades, short or long, with up to 100X leverage. User balance and rank is tracked on a leaderboard and can be displayed as flair on r/BitcoinMarkets.

  • All users start with a balance of $100,000 but can pay sats to reload their balance at a rate of 1sat/$10.
  • Trades are opened/closed at the Coinbase Pro price the moment Bitty Bot sees the trade command. Prices cannot be specified by the user or changed after a trade is entered.
  • Limit Commands can be used to set trades (or close or edit a trade stop loss/take profit) to execute at exact prices, with no slippage, in advance.
  • Users can trade with up to their full balance, or $5,000 (plus leverage), whichever is greater. This is because balances are allowed to go negative and users will still be able to place trades with up to $5,000 (plus leverage) to try and dig themselves out of the hole.
  • Trades are limited to a maximum size of $100 Million to be more realistic. This only affects users with very large balances.
  • Funding rates are always 0%. The Bitty Bot Bank does not charge interest!
  • Trades are priced in USD, NOT in BTC. For example: Opening a long with $10,000 will long $10,000 worth of BTC at the current price.
  • Users can have only 1 trade open at a time. Opening a new trade will immediately close your current one, if any, and open a new one at the current price. This allows you to quickly replace an existing trade with a new one at the same price, with no slippage.
  • Leverage can be any amount from 1X to 100X
  • Stop loss and take profit prices are optional and can both be added to any trade. There will be no slippage. If your stop loss or take profit price is hit, your trade will close at exactly that price.
  • Liquidation price, based on the leverage used, will be calculated and displayed when you open a trade. If your liquidation price is hit, your trade will be closed at that exact price (with no slippage) and you will lose your initial investment.
  • Users will be ranked based on their Total Profit & Loss (PnL). Total PnL = Cash Balance + Unrealized Profit Or Loss from any open trade, minus starting cash ($100k) and reloaded cash.
  • Users can share their Total PnL as Subreddit Flair on r/BitcoinMarkets by chosing the Bitty Bot Paper Trading flair in the subreddit sidebar. Once this flair is selected, the bot will continuously update your flair every 10mins, or every 1% price move, or any time any trade is opened or closed.
  • Unrealized PnL & Rankings are updated near-instantly on the website on all pages.
  • r/BitcoinMarkets is our home. Please be respectful of other users. If you are often opening and closing trades without context, please do it via direct message, in an old daily thread, the Bitty Bot Trade Log thread, or in the dedicated Bitty Bot sticky comment to prevent unneeded spam.

    !bitty_bot long|short USD-amount [leverage amountX] [sl stop loss price] [tp take profit price]

  • long|short Required: Whether your trade is long or short.
  • USD-amount Required: The total amount of BTC to trade. Example: $50,000. MAX can also be used here to calculate the maximum trade amount, based on your current cash balance, and selected leverage.
  • [leverage amountX] Optional: The amount of leverage to use to trade the specified USD-amount of BTC. Can be any amount 1X-100X. Default is 1X. Example: 5X
  • [sl stop loss price] Optional: The price to set a stop loss at. If the price hits your stop loss price, your trade will be immediately closed at your stop loss price (no slippage). Example: sl $40,000
  • [tp take profit price] Optional: The price to close the trade and take profit at. If the price hits your take profit price, your trade will be immediately closed at your take profit price (no slippage). Example: tp $78,000

!bitty_bot edit [sl stop loss price | remove] [tp take profit price | remove] - Used to edit, add, or remove SL and TP. If SL or TP is not specified, they will NOT be changed. The SL or TP will be removed if you specify 'remove' after sl or tp.

!bitty_bot close [XX%] - Immediately closes any open trade. If you do not wish to close your entire trade, you can close only some of it by specifying a percentage to close.

!bitty_bot limit limit-price trade-command - Sets a limit command at limit-price. Trade-command is a normal Bitty Bot long, short, close, or edit command that will execute at the limit-price. See Limit Commands Section and Examples below.

!bitty_bot ATH - Responds with the Bitcoin All Time High from Coinbase and the date and time it was set.

!bitty_bot reload number-of-sats - Generates a Lightning invoice for you to pay the specified number of sats to reload your balance at 1 sat/$10. Click Here to easily send this command, just fill in the number of sats.

When you use leverage to paper trade, you are borrowing money from the Bitty Bot Bank to trade with. For example, if you write the command !bitty_bot long $20,000 10X you will be longing a TOTAL of $20,000 worth of BTC.
$2,000 will come from your cash balance and $18,000 will be borrowed from the Bitty Bot Bank.

However, using leverage puts you at risk of liquidation. Sticking with the same example, let's assume the current price of Bitcoin is $50,000. Longing $20k means you longed 0.4BTC ($20k/$50k). This means your liquidation price would be $45k ($50k*(1-(1/10X))).
If the price of Bitcoin touches $45k or below, the 0.4BTC is now worth only $18k (0.4*$45k), the amount you borrowed from the Bitty Bot Bank.
Bitty Bot forces your trade to close, pays the Bank back the $18k you borrowed, and the $2k spent from your cash balance is lost.

Stop losses can be used to automatically close a trade before your liquidation price is hit, preventing a total loss on a trade.

Leverage Formula: Cash_Spent = Total_Amount * (1 / Leverage_Amount)
Ex: $2,000 = $20,000 * (1 / 10X)

Liquidation Price Formula: Liquidation_Price = Trade_Open_Price * (1 - (1 / Leverage_Amount * -1_If_Short))
Ex: $45,000 = $50,000 * (1 - (1 / 10X))

Stop loss and take profit prices can be used to trigger a trade to close automatically at a certain price. A trade can have a stop loss price, take profit price, or both, or neither.

If the price of Bitcoin is currently $50k and you write the command !bitty_bot long $20,000 10X sl $48,000 tp $59,000 you are setting a stop loss at $48k and a take profit at $59k.

In this trade, you are longing 0.4BTC and your liquidation price is $45k, resulting in a total loss of your $2k in cash if liquidated. However, due to the stop loss at $48k your trade would be automatically closed (with no slippage) if the price of BTC hits $48k or below.
Closing at $48k would result in $1,200 (($48,000 * 0.4) - $18,000) returning to your cash balance, only an $800 loss vs the total loss of $2,000 if liquidated.

On the other side, if the price of BTC hits $59k or above, your trade will be automatically closed (with no slippage) at $59k to lock in a profit of $5,600 (($59,000 * 0.4) - $18,000) that will be added to your cash balance.

You can use the "edit" command to add, change, or remove your SL and TP at any time without closing your trade. Example: !bitty_bot edit sl $48,000 tp remove

Due to the limitation of only being able to have one trade open at a time, it is not currently possible to "hedge" a long-term long trade with a temporary short trade, or vice versa. However, this can be worked around by being able to instantly replace one trade with another, with no slippage.

For example, if you currently have a 10X long open because you are long-term bullish, but think the BTC price could go down in the short term, you can instantly replace your 10X long with a lower-leverage long, or a short, simply by placing a new trade.

Placing a new trade will instantly close your current trade at the current price, and open your new trade at that same price, with no slippage.

This feature allows you to quickly "hedge" or reposition your trade without having to first close your existing trade and risking the market price changing rapidly before you can open your new trade in times of high volatility.

To utilize this feature, simply write a new trade command. Bitty Bot will close your current trade and open the new one in a single response.

Limit Commands allow you to set long and short paper trades (or close or edit a trade) in advance that will trigger at a certain price, the Limit Price.

For example, if the current price is $50k and you would like to place a 100X short with your MAX balance if we drop to $49k the command would be !bitty_bot limit $49,000 short max 100x

Limit Commands also allow you to set a partial close, or edit a Stop Loss or Take Profit at a certain price, to set things like trailing stop losses!

!bitty_bot limit list is used to view and delete your set limit commands.

!bitty_bot limit delete all is used to immediately delete all your set limit commands.

When a Limit Command is triggered, the trade command (after the limit price) will be immediately run and open your trade as if you sent the command to Bitty Bot manually. This means if you have a trade open when the limit command is triggered, your open trade will be closed at the limit price and your limit command will execute at the limit price.

Note: Trade commands on limit orders are not verified UNTIL THE LIMIT COMMAND TRIGGERS. If you have a typo in your trade command, or you do not have sufficient balance to open the trade, the trade open will fail. If you have a trade open when your limit command triggers, and the trade command cannot open your new trade, your existing trade will still be closed! Watch out for typos!

See Paper Trading Command Examples below for more Limit Command examples.

For all examples, assume the current BTC price is $50,000.

!bitty_bot long $50,000 - 1 BTC is longed at 1X (no leverage). $0 is borrowed from the Bitty Bot Bank and $50k is deducted from the user's cash balance. Cannot be liquidated due to 1X leverage. No stop loss or take profit is set.

!bitty_bot short $100,000 5X - 2 BTC is shorted at 5X. $80k is borrowed from the Bitty Bot Bank and $20k is deducted from the user's cash balance. Liquidation price = 50,000 * (1 - (1 / 5X * -1)) = $60,000, -1 is added to the calculation due to it being a short. No stop loss or take profit is set.

!bitty_bot long $2,000,000 20X sl $48000 - 40 BTC is longed at 20X. $1,900,000 is borrowed from the Bitty Bot Bank and $100k is deducted from the user's cash balance. Liquidation price = 50,000 * (1 - (1 / 20X)) = $47,500. A stop loss is set at $48,000.

!bitty_bot short $1,000,000 50X tp $45000 - 20 BTC is shorted at 50X. $980,000 is borrowed from the Bitty Bot Bank and $20k is deducted from the user's cash balance. Liquidation price = 50,000 * (1 - (1 / 50X * -1)) = $51,000. A take profit is set at $45,000.

!bitty_bot long $5,000,000 100X sl $49900 tp $52000 - 100 BTC is longed at 100X. $4,950,000 is borrowed from the Bitty Bot Bank and $50k is deducted from the user's cash balance. Liquidation price = 50,000 * (1 - (1 / 100X)) = $49,500. A stop loss is set at $49,900. A take profit is set at $52,000.

!bitty_bot long MAX 100X sl $49900 tp $52000 - If the user still has a balance of $100k, 200 BTC is longed at 100X. $9,900,000 is borrowed from the Bitty Bot Bank and $100k is deducted from the user's cash balance. 'MAX' calculates the maximum trade amount based on the user's cash balance and selected leverage. Liquidation price = 50,000 * (1 - (1 / 100X)) = $49,500. A stop loss is set at $49,900. A take profit is set at $52,000.

!bitty_bot edit sl $45000 - A stop loss is set to $45,000 for your currently open trade and a take profit, if set, is NOT changed.

!bitty_bot edit sl $45000 tp $49000 - A stop loss is set to $45,000 for your currently open trade and a take profit is set to $49,000.

!bitty_bot edit tp $49000 - A take profit is set to $49,000 for your currently open trade and a stop loss, if set, is NOT changed.

!bitty_bot edit tp remove - A stop loss, if set, is NOT changed and a take profit, if set, is removed for your currently open trade.

!bitty_bot edit sl remove tp $48000 - A stop loss, if set, is removed and a take profit is set to $48,000 for your currently open trade.

!bitty_bot edit sl remove tp remove - A stop loss, if set, is removed and a take profit, if set, is removed for your currently open trade.

!bitty_bot close - 100% of any open trade is immediately closed at the current price.

!bitty_bot close 60% - 60% of your currently open trade is closed and 40% is left open.

!bitty_bot limit $49k long max 10x sl $47k - The current price is $50k. You want to long a dip from $49k. If the price falls to $49k or lower, your current trade, if any, will be closed at $49k and long max 10x sl $47k will be executed at $49k.

!bitty_bot limit $51k short $500,000 20x sl $52k tp $48,500 - The current price is $50k. You want to short a pump to $51k. If the price rises to $51k or higher, your current trade, if any, will be closed at $51k and short $500,000 20x sl $52k tp $48,500 will be executed at $51k.

!bitty_bot limit $52k long max 20x - The current price is $50k. You want to long a breakout above $52k. If the price rises to $52k or higher, your current trade, if any, will be closed at $52k and long max 20x will be executed at $52k.

!bitty_bot limit $48k short $500,000 20x sl $50,500 tp $46,500 - The current price is $50k. You want to short a breakdown below $48k. If the price falls to $48k or lower, your current trade, if any, will be closed at $48k and short $500,000 20x sl $50,500 tp $46,500 will be executed at $48k.

!bitty_bot limit $48k close 50% - The current price is $50k. You want to close 50% of your short if the price falls to $48k. If the price falls to $48k or lower close 50% will be executed at $48k.

!bitty_bot limit $48k edit sl 48100 - The current price is $50k, you have a short open. If the price falls to $48k or lower, you want to edit your Stop Loss to $48,100 to set a "Trailing Stop Loss". edit sl 48100 will be executed at $48k.

!bitty_bot limit list - Responds with a list of your currently set limit commands along with a link to delete each one.

!bitty_bot limit delete all - Immediately deletes all your set limit commands.

!bitty_bot ATH - Responds with the Bitcoin All Time High from Coinbase and the date and time it was set.

!bitty_bot reload 10000 - Responds with an invoice to pay 10000 sats via the Lightning Network to add $100k to the user's balance (1 sat/$10).

Paper Trading Balance Reloads

    Your Paper Trading Balance is allowed to go negative forever, but when it falls below $5k, you are limited to placing trades with a max size of $5k + leverage until your balance is positive and above $5k again.

    To get around this limitation, Bitty Bot allows users to send sats to pay to reload their balance. Reloading is inexpensive, 1 sat will reload your balance $10. So sending 10,000 sats (worth $) will add $100,000 to your balance.

    You can reload an unlimited number of times. But for fairness you can only reload if your balance is below $100,000 and you can never reload your balance to be higher than the original $100k everyone starts with. For example, if your balance is -$200k you can reload a max of $300k to get your balance back to $100k.

    When you send me the !bitty_bot reload number-of-sats command, I will respond with a Lightning Network Invoice for that number of sats, as well as an Invoice QR Code. You can copy and paste that invoice, or scan the QR Code, into the Exchange or Lightning Wallet you are using. Once the invoice is paid, I will immediately send you a confirmation message and credit your Paper Trading Balance the reloaded amount!

    To pay the Lightning Invoice, any Lightning Wallet, or Exchange that supports Lightning Withdrawals will work. We love that Kraken supports FREE Lightning Withdrawals, meaning you can pay the invoice with your BTC Balance directly from your Kraken account. We also recommend the following Lightning Wallets: Wallet of Satoshi, Phoenix, and Breez. All of these wallets allow users to move on-chain BTC to Lightning by paying a one time on-chain fee. Any other Lightning Wallet will also work.

    If you are new to the Lightning Network, please do your own research when selecting a wallet or exchange and feel free to reach out if you have any questions. I'm always happy to help!

    All sats paid to Bitty Bot are put into the Prize Pool to be used as prizes for future Trading Tournaments. Bitty Bot is about bringing fun and new features to the subreddit, not making a profit of a few sats.

    Note: Reloading your balance will NOT move you up the Paper Trading Leaderboard. The Leaderboard ranking is based on Total PnL and reloading your balance will not change your PnL.

    Reload Your Balance!

User Options

User Options allow the user to set options that affect the way the user interacts with Bitty Bot.

For example, there is an option to require a Stop Loss when opening a trade. If a user sets this option to True and mistakenly tries to open a new trade without a Stop Loss, an error will be thrown.

  • Options change Bitty Bot's default behavior and are considered an Advanced Feature. Most users will never want to change options from their default values.
  • Use the !bitty_bot options list command to get started setting User Options.

pt_require_sl True|False (Default: False) - Paper Trading: If True, require Stop Loss when creating a trade. Will throw an error on trade creation if a stop loss is not specified. (Careful: this applies to limit commands too!)

Let me know if you have ideas for new options! Thanks to u/btc-_- for suggesting this feature and the pt_require_sl option.

!bitty_bot options list - Lists all available options and the current value with links to send commands to change each.

!bitty_bot options edit option_name option_value - Edits an option. Normally this command is not used manually, but is instead sent when you click the links in the reply you get from the !bitty_bot options list command. However, it can be sent manually if desired.

!bitty_bot options list - Lists all available options and the current value with links to send commands to change each.

!bitty_bot options edit pt_require_sl True - Sets the pt_require_sl option to True for the user. All future trades will require a Stop Loss or an error is thrown.

!bitty_bot options edit pt_require_sl False - Sets the pt_require_sl option to False for the user. All future trades will NOT require a Stop Loss.

Bitty Bot Changelog

  • Nov 20 2024 - Add "Paper Trading Command Builder" to all user profile pages. This command builder allows you to build a paper trading command on the site, see estimated liquidation levels, estimated PnL for Stop Losses and Take Profits and then click a button to send the command directly to Bitty Bot. Massive thanks to u/btc-_- for testing this over and over and over!
  • Nov 08 2024 - If a new ATH is set, announce it in the stickied post at the top of the current Daily Thread
  • Oct 31 2024 - Add Predictions Flair for users that shows their prediction rank, correct prediction count, and wrong prediction count
  • Oct 31 2024 - Paper Trading is now disabled when Coinbase is down (such as during maintenance) so that users cannot use maintenance events to place unfair trades
  • Oct 31 2024 - Fix race condition where trade close message may not be published to Reddit if a trade is closed almost immediately after open (thanks u/Antranik!)
  • Oct 28 2024 - Fix user profile page if user has 0 closed trades but has a trade open
  • Oct 16 2024 - Add counts for correct predictions and wrong predictions to the predictions leaderboard stats
  • Sep 25 2024 - Added the ability for users to make predictions that trigger at an exact time, no matter what the price does before then, by putting = in front of the prediction date or time from now. See updated predict command documentation above.
  • Sep 22 2024 - Added "pt_require_sl" user option. Default: False. If set to True an error will be thrown if a user tries to open a new trade without a Stop Loss set.
  • Sep 22 2024 - Added "User Options" feature to allow users to set options that affect the way they interact with Bitty Bot (See User Options section above)
  • Sep 22 2024 - Add website button to send commands to Bitty Bot so that hopefully users stop trying to send commands to the inbox that is for feedback, suggestions, and questions
  • Sep 17 2024 - Added prediction stats for all currently open predictions (prediction counts, highest and lowest price predictions, nearest and furthest date predictions) to the top of the Prediction Leaderboard
  • Sep 13 2024 - Greatly increase the use of muliprocessing so Bitty Bot finds commands quicker, the website updates quicker, and responses to commands are quicker. 1-5 seconds are saved on each step
  • Sep 08 2024 - To reduce the amount of comments made by Bitty Bot, we will no longer reply to a trade open/close command with a link to the trade log. Instead, we will only comment in the trade log and tag the user (make sure you have tag notifications on!)
  • Sep 07 2024 - Add optional message that can be included in Bitty Bot notifications
  • Sep 06 2024 - Prevent users from adding multiple predictions at the same price, as they will always trigger at the exact same time and could be gamed by users to get multiple correct predictions at once
  • Sep 02 2024 - Drastically improved website efficiency. Less data is now transferred resulting in faster page updates, especially on mobile
  • Aug 27 2024 - Add dark theme to website. Light/dark theme triggers based on user's OS setting
  • Aug 25 2024 - Add max trade amount of $100 Million
  • Aug 24 2024 - Replaced the HH:MM:SS timestamp of when a prediction was added, with the price at the time the prediction was created as this seems like more relevant data
  • Aug 24 2024 - Removed 'pnl' command since it is unused now that the website displays all of this data live
  • Aug 18 2024 - Removed decimals from nearly all numbers on the website for mobile users only. Allows the tables to be more compact without losing much useful data
  • Aug 17 2024 - Full re-write of all website pages so that all data on all pages is updated automatically and near-instantly from API
  • Aug 11 2024 - Add Prediction and Paper Trading rank changes over the last 7 days to both leaderboards
  • Aug 11 2024 - Rank tied users deterministically. Previously users that were tied on any leaderboard could change order within that tie on page refresh. This has been fixed
  • Aug 09 2024 - Add Prediction and Paper Trading rank changes over the last 7 days to user details page
  • Aug 08 2024 - Sort "Historical Prediction" table by triggered date time instead of the date time the prediction as added to make it easier to see recently triggered predictions
  • Aug 08 2024 - For all expired predictions, show the expiration date as the date time the prediction was marked correct/wrong, instead of only showing the expiration date the user put in the prediction
  • Aug 02 2024 - Added `!bb` as a Bitty Bot Trigger option, since it is easier and faster to type than `!bitty_bot`
  • Aug 02 2024 - Added Liquidation/SL/TP prices to all tables on the site where trades are shown. Closed trades only show stop loss or liquidation price. Open trades will also show the take profit price
  • Jul 31 2024 - Added predictions User Details Profile Page and also added predictions to the chart as color coded dots
  • Jul 25 2024 - Added new User Details Profile Page for each user that shows trading stats, trading balance chart and all trades for each user. Eventually this will include predictions as well
  • May 01 2024 - Added "range" predictions. Uses the symbol "<>" to predict the price will trade within a range until the specified date. Example: <> $25k-$35k
  • Apr 30 2024 - Added the ability to parse weekdays such as Monday, Tuesday, Wednesday, etc to the Date and Time options
  • Apr 28 2024 - In addition to Long and Short trades, allow "close" and "edit" commands to be set as "Limit Commands". Rename all "Limit Trades" to "Limit Commands"
  • Apr 19 2024 - All predictions have been audited. Predictions that appeared to be trying to game the system and log obviously correct predictions have been deleted. If you notice someone else doing this and believe a prediction needs review, please message me here.
  • Apr 16 2024 - Updated Limit Trade Section of the paper trading page to work better with the upcoming Limit "Command" feature.
  • Apr 16 2024 - Prediction time frames now default to 30 days if not set. You can no longer set a prediction that does not have an expiration time frame (Never is still valid). If a time frame is not set when the prediction is added, 30 days will be used.
  • Apr 11 2024 - Fix website scrolling when linking directly to a user's predictions or paper trading section of the leaderboard.
  • Mar 27 2024 - Moved all Coinbase API calls to use the Advanced Trade Websockets. This means every single trade, sometimes hundreds per second, that happens on Coinbase is now processed by Bitty Bot. Meaning instant reactions to wicks instead of having to rely on checking candles from the Coinbase API for wicks (candles are still checked as a backup).
  • Mar 27 2024 - Completely reorganized Bitty Bot's main event loop to be far more performant and efficient. Responses to commands are now as fast as the Reddit API will show them and responses to prices from the Coinbase API are instant.
  • Mar 24 2024 - Paper Trading Leaderboard now only loads recent trades and has buttons to load in historical trades (previously these were just hidden, but still in the page data) via a new API. This means much faster leaderboard page load time!
  • Mar 22 2024 - Improved usability of Paper Trading Leaderboard Page. Clicking on a username on the leaderboard will open their trade history. Clicking on a username in the open or closed trades list will scroll you to their spot on the leaderboard and open their history.
  • Mar 22 2024 - Add open predictions to the Prediction Leaderboard so that you can see all of a user's predictions, open and closed, at a single link like https://bittybot.net/predictions#garycomehomee
  • Mar 22 2024 - Improved usability of Predictions Leaderboard Page. Clicking on a username on the leaderboard will open their prediction history. Clicking on a username in the current or historical predictions list will scroll you to their spot on the leaderboard and open their history.
  • Mar 21 2024 - Now that we have Auto Refresh on the Paper Trading Leaderboard, no longer update that page every 5 minutes, only update it when any trade is opened or closed.
  • Mar 20 2024 - When a user's leaderboard history is collapsed, remove `#username` from the URL so that if the page is refreshed it does not scroll back to that user
  • Mar 20 2024 - Add `!bitty_bot limit delete all` to delete all open limit trades for a user
  • Mar 19 2024 - Completed "move all data to a more reliable and performant database". whew.
  • Mar 18 2024 - Randomize Reddit User Icon Cache update so that all user icons do not refresh at the same time and cause the Reddit API to rate limit me
  • Mar 11 2024 - Make !bitty_bot ATH command also print the % away from current ATH (thanks u/make_n_bake!)
  • Mar 10 2024 - Add 'ATH' price keyword that will sustitute the all time high price in any Bitty Bot command where a price is specified, such as predictions, notifications, trades, etc.
  • Mar 10 2024 - Add !bitty_bot ATH command to print all time high price and the date and time it was set
  • Mar 09 2024 - For fairness, Paper Trading reloads are limited so that users can only reload if their balance is below $100k and they cannot reload their balance to be more than the $100k everyone originally starts with
  • Mar 04 2024 - Began work to move all data to a more reliable and performant database
  • Mar 03 2024 - Auto update PnL on Paper Trading Leaderboard. Auto refresh page if trade is opened or closed
  • Feb 23 2024 - Added Limit Trades. See updated documentation above. Thanks to u/Antranik for testing!
  • Feb 20 2024 - On both leaderboards you can now create links that scroll directly to and then expand a user's prediction/trade history example: https://bittybot.net/paper-trading#Antranik
  • Feb 20 2024 - BREAKING CHANGE: For the Paper Trading 'edit' command, only remove SL or TP if 'remove' is specified (see edit command docs)
  • Feb 19 2024 - Fixed a bug that caused partial closes to inflate PnL (thanks to u/Antranik) also retroactively corrected all previous partial close trades so they have the correct PnL
  • Feb 13 2024 - Predictions now include a link other users can click to also be notified when the prediction is triggered
  • Feb 13 2024 - Removed permalink buttons on leaderboards. Added trade/prediction open link and trade close link to open/close date to make tables more compact
  • Feb 09 2024 - Paper Trading Leaderboard now updates every 5 minutes, or every 0.5% price move, or any time any trade is opened or closed. These values used to be 30 minutes and 1%
  • Feb 06 2024 - Predictions now include a link that the Predictor can click to delete the prediction if it was made in error
  • Jan 31 2024 - Send users important messages such as low Paper Trading Balance, and a welcome message after their first trade
  • Jan 28 2024 - Allow users to reload their paper trading balance by paying sats over the Lightning Network at a rate of 1sat/$10 with the "reload" command
  • Jan 28 2024 - Add the ability to partially close a trade with the !bitty_bot close XX% command
  • Jan 20 2024 - Fix a bug that could cause a SL or TP to be triggered incorrectly if it was added within 60 secs of trade open
  • Jan 20 2024 - Allow users to send all commands as direct message instead of having to post them as comments in the subreddit
  • Jan 15 2024 - Add Paper Trading Statistics to Paper Trading Page
  • Jan 15 2024 - Make subreddit flair show PnL instead of just balance
  • Jan 14 2024 - Check every Coinbase 1min candle against all notifications, predictions, and trades to ensure no wick during high volatility is ever missed
  • Jan 11 2024 - Add 'edit' command to allow users to edit the SL and/or TP of currently open trade
  • Jan 08 2024 - Add 'pnl' command to allow users to quickly see their PnL for currently open trade
  • Jan 07 2024 - Update user flair in r/BitcoinMarkets
  • Jan 05 2024 - Fix bug that could cause liquidation even if user has stop loss set
  • Jan 01 2024 - 'max' trade amount is added to auto calculate the maximum amount a user can trade with
  • Jan 01 2024 - 'k' and 'm' added as suffixes to represent thousands and millions, respectively
  • Jan 01 2024 - Paper Trading Officially Launches
  • Dec 31 2023 - Trade confirmations and other Bitty Bot comments are moved to a trade log post to prevent reddit spam
  • Dec 30 2023 - Paper Trading Beta Period Starts
  • Dec 22 2023 - BittyBot.net is launched with leaderboards and documentation
  • Dec 19 2023 - Inverted predictions are added
  • Dec 14 2023 - Bitty Bot Launches with Price Predictions and Notifications

Need help? Have a suggestion? Get in touch!

Bitty Bot loves to hear from his users. Whether you have an idea for a new feature, want to report a bug, or just need some help getting the command right for your prediction or trade, shoot over a message!

Message Bitty Bot