How to download and import templates into Compass Automations
Import the automation templates mentioned in this article by pasting the share string into beta.compass.art/automations/templates > Import template. To do this you need access to Compass Automations Beta, given out in our Discord.
1. Smart OS bidder
This template allows you to constantly outbid the top bid on Opensea by placing collection bids every 10 minutes. Each bid has a 10 minute expiration (the minimum expiration allowed by OS) therefore you’ll have 1 bid active at any moment. You won’t keep outbidding yourself as by the time you post your next bid the previous one will have just expired. You can enter an upper bid limit, an outbid top bid by amount and a stop after x purchases value. The template has an alert that sends you a telegram/discord message every time you make a bid.
By default the bid action is disabled with a bid simulation alert in front of it. Before activating the bidding step, test the automation on your collection with the simulator alert sending simulated bids to your telegram/discord. Only activate the bid action once you made sure the simulated bids are as expected.
minspreadmargin: The minimum bid/ask spread profit margin that you are willing to bid on. The bid/ask margin is the price difference between the top bid and listing floor on OS after 0.5% fees. Default value is 0.018 as that is the typical gas fee for an OS transaction. If you don’t care about the minimum spread margin then set this as 0. Example: I expect to pay 0.018 gas when I’m selling my NFT through a listing. When my bid gets accepted the seller pays the gas so my costs will be 0 there. I also want to have at least a 0.01 profit after all costs when I flip the token on floor. Therefore I’ll use a minspreadmargin of 0.028. In this case if the difference between the floor and top bid is less than 0.028 the bot will not place a bid. It will only place bids if the difference is more than 0.028.
Wallet: Your bids will be placed from this wallet.
Upperbidlimit: The absolute maximum the bot will bid. If the top bid + out bid by is more than this value the bot will not bid.
Collection: The bot will place collection bids on this collection Outbidtopbidby: The bot will outbid the highest bid by this much
Stopafterxbuys: Once you have this number of tokens from this collection in your wallet, the bot will stop bidding. Useful to limit your exposure to a collection. Example: I’m bidding on Azukis and have set my stopafterxbuys to 5. The bot will keep bidding until there are 5 Azukis in my wallet. If I manage to sell an Azuki and it goes back to 4, the bot will resume bidding.
Goes well with: Autolister. Buy Alert
2. Blur Points Farmer with Undercut
This template allows you to farm BLUR points by placing collection bids right below the top bid bracket on BLUR. It can undercut the top bid by any amount you specify. Each bid has a 15 minute expiration (the minimum expiration allowed by BLUR).
Example: The otherdeeds top bid is 1.86. If you set it up like this: Maxbid: 2 Undercutby 0.02 then it will bid 1.84, as it undercuts the top bid of 1.86 by 0.02. If the top bid moves up to 2.02 then you'd normally bid at 2. However, since you have a max bid of 2 set, it will not bid.
By default the bid action is disabled with a bid simulation alert in front of it. Before activating the bidding step, test the automation on your collection with the simulator alert sending simulated bids to your telegram/discord. Only activate the bid action once you made sure the simulated bids are as expected.
Collection: The bot will place collection bids on this collection
Wallet: Your bids will be placed from this wallet.
Maxbid: The absolute maximum the bot will bid. If the top bid + out bid by is more than this value the bot will not bid.
Undercutby: The bot will undercut the top bid by this amount
Goes well with: Auto List on BLUR+OS, Buy Alert
3. Auto List on BLUR+OS
This templates auto lists a token on BLUR and OS every 15 minutes. It can undercut or list above floor thanks to the Listmarkup field. If the floor falls below your token purchase price by the rate indicated in the stoplossmultiplier the listing will not go through and you’ll get an alert instead. This is useful to protect from floor price manipulators.
By default the OS and BLUR List actions are disabled with a list simulation alert in front of them. Before activating the listing steps, test the automation with the alert sending simulated lists to your telegram/discord. Only activate the list actions once you made sure the simulated lists are as expected.
Collection ID: This collection’s token will be listed
Token: This token will be listed. To auto list freshly bought tokens, use with the Buy trigger template
Listmarkup: Lists relative to floor. E.g. list markup of 1.1 lists 10% above floor. 0.8 lists 20% below floor
Stoplossmultiplier: Indicates how much the floor has to fall below your purchase price to stop listing and send you a warning alert instead. A stoplossmultiplier of 0.8 would stop listing and trigger an alert if the floor price dropped 20% below your purchase price. Useful to protect from floor manipulators.
Goes well with: Smart bidder, Blur points farmer with undercut
4. Stop Loss Alert
This template sends you a Telegram/Discord message when one of your NFTs goes into unrealized loss. You can specify the size of unrealized loss that will trigger the alert, compared to your purchase price with the stoplossat input. For example a stoplossat 0.8 will send an alert when the floor has dropped 20% below your purchase price. The alert includes a quick link to your Opensea wallet holdings. This automation will check your unrealized PnL for a specified token every minute, then if the Stop Loss is triggered, the automation will send you an alert and sleep for 6 hours. This is to keep the automation's reactions quick all while avoiding spam alerts to your phone.
Wallet: The Stop Loss Alert will monitor a token from this wallet.
Collection ID: The Stop Loss Alert will monitor a token from this collection.
Token: The Stop Loss Alert trigger for this token.
Stoplossat: The rate of loss compared to the purchase price that will trigger the alert. e.g. with a stoplossat of 0.7 and a purchase price of 10 eth, the alert will trigger if the floor drops below 7 eth.
Sleepafteralert: The sleep time after a stoploss alert is triggered.
Stoplossmultiplier: Indicates how much the floor has to fall below your purchase price to stop listing and send you a warning alert instead. A stoplossmultiplier of 0.8 would stop listing and trigger an alert if the floor price dropped 20% below your purchase price. Useful to protect from floor manipulators.
Goes well with: Buy Trigger for Stop Loss Alert
5. Take Profit Listing
This template Lists one of your NFTs on BLUR and OS when a given unrealised profit is reached. The takeprofitmultiplier indicates the rate of unrealized profit compared to the token's purchase price that will trigger the listing on floor. For example a takeprofitmultiplier of 1.4 will list the token when the floor rises 40% above your purchase price.
By default the OS and BLUR List actions are disabled with a list simulation alert in front of them. Before activating the listing steps, test the automation with the alert sending simulated lists to your telegram/discord. Only activate the list actions once you made sure the simulated lists are as expected.
Collection ID: The Take Profit Listing Automation will monitor a token from this collection.
Token: The token ID you'll list for sale, fromat: collectionid_tokenid
Takeprofitmultiplier: The takeprofitmultiplier indicates the rate of unrealized profit compared to the token's purchase price that will trigger the listing on floor. For example a takeprofitmultiplier of 1.4 will list the token when the floor rises 40% above your purchase price.
Goes well with: Buy Trigger for for Take Profit Listing
6. Dump Sniper
This template will monitor wallets (dumpers) dumping a lot of tokens from a collection into bids, and snipe the last two tokens from its holdings. As the dumper burns through the top of the bid ceiling he is accepting lower on lower offers on his tokens, temporarily widening the bid/list spread. Thus, there is a brief opportunity for deep discounts on one or two tokens from the collection. This automation will trigger when someone accepting offers one after the other has already sold two tokens 20% below floor. Then it will check how many tokens remain in his wallet and if there is 1-2 tokens left, it will outbid the top bid on them as long as the bid is x% below the floor. The x% is determined by the discounttarget input, for example a discounttarget of 0.5 would mean the top bid on the two remaining tokens must be less than 50% of the floor. The automation also has a maxbid input, which is a hard cap on the maximum eth you are willing to bid. The minvolume variable is the minimum lifetime volume of the collection in eth. If you specify 100 eth for the minvolume, the automation will ignore all collection that have less than 100 eth of lifetime volume. This is to filter out low volume, and therefore riskier collections. This automation can earn money by getting good deals on relatively low volume collections that have relatively thin bid ceilings that whales can burn through when dumping. There is no wallet filter in this automation so it monitors all transactions on the blockchain. If a dumper sells two tokens within 15 minutes, the automation will immediately trigger after the second sale.
Example use case: We're siniping dumpers with a minvolume of 100 eth, maxbid of 0.8 and discounttarget of 0.5. Whale X decides he wants to exit low liquidity collection because he needs the money fast. He knows that selling his tokens through listings his will take a lot of time and therefore decides to simply accept the 10 best collection bids for his 10 tokens. The collection he is about to dump has 250 eth of lifetime trading volume, and the floor sits at 1 eth. The bid ceiling for this collection is thin, but stands at 0.9 eth. After accepting the first two bids within 15 minutes of eachother, our automation triggers and counts how many tokens he still holds. The whale still holds 8 tokens so nothing happens. When the whale is down to 2 tokens left, the automation will continue by looking at the top bids on these two remaining tokens. By now the bid ceiling, and therefore the top bids on his last two tokens is down to 0.4 eth. As 0.4 eth is less than the 1 eth floor times our discounttarget of 0.5 (50%) the bot will bid 0.4001 eth on the whales two remaining tokens. If the whale decides on continuing his dump, he will accept our bids on these two tokens, letting us acquire tokens at 0.4001 eth instead of the 1 eth floor or the 0.9 eth bid ceiling just minutes ago. By default, the automation will not bid on collections that din't have a single sale in the last 14 days to avoid bidding on dead collections.
By default the bid action is disabled with a bid simulation alert in front of it. Before activating the bidding step, test the automation on your collection with the simulator alert sending simulated bids to your telegram/discord. Only activate the bid action once you made sure the simulated bids are as expected.
Minvolume: Minimum required lifetime volume of the collection a whale is dumping. Useful to avoid the lowest liquidity and therefore riskiest collections.
Maxbid: A hard cap on the maximum eth you are willing to bid
Discounttarget: The minimum bid/floor spread that is required by the time the whale has 2 tokens left to place bids.
7. Bulk Lister
This template allows you to list your tokens in bulk without flooding the market. It enables you to list a specific number of tokens, as specified by the input parameter countoftokenstolist, at gradually increasing prices, starting from the floor prices on both the BLUR and OS marketplaces. The increment in the listing prices is determined by the input parameter listingladderincrement. The tokens will be listed on both the BLUR and OS marketplaces based on their specific floors. The listing prices will be readjusted every 15 minutes relative to the floor price. This ensures that all listings are readjusted in the event of any fluctuations in the floor price. The absolute lowest listing price the automation will list for is specified by the Listlowerlimit input parameter. The formula for determining the listing price is as follows: floor + (floor x increment x index), rounded to 4 decimal places.
For instance, let us assume that Collection Azuki has a floor price of 0.2 ETH on OS and 0.1 ETH on BLUR, and you hold 10 tokens. If you set countoftokenstolist to 5, listingladderincrement to 0.1, and Listlowerlimit to 0.12, the automation will list five of your tokens at gradually increasing prices, as shown below:
OS listings:
Token 1 listing price: 0.2 ETH
Token 2 listing price: 0.22 ETH
Token 3 listing price: 0.24 ETH
Token 4 listing price: 0.26 ETH
Token 5 listing price: 0.28 ETH
BLUR listings:
Token 1 listing price: 0.12 ETH (normally 0.1 ETH, but this is lower than your Listlowerlimit of 0.12)
Token 2 listing price: 0.12 ETH (normally 0.11 ETH, but this is lower than your Listlowerlimit of 0.12)
Token 3 listing price: 0.12 ETH
Token 4 listing price: 0.13 ETH
Token 5 listing price: 0.14 ETH
By default, the automation disables the listing actions for both BLUR and OS, and displays a list simulation alert. Before activating the listing step, it is recommended to test the automation using the simulator alert, which sends simulated lists to your Telegram or Discord. Only after verifying that the simulated lists are as expected should you activate the list actions.
Collection: Tokens will be listed from this collection
Wallet: Tokens will be listed from this wallet
Listingladderincrement: The incremental list price increase between your tokens. For instance, a value of 0.1 would mean that each listing will be 10% more than the previous listing.
Countoftokenstolist: The number of tokens the automation will list.
Listlowerlimit: The absolute lowest listing price the automation will list for.
This automation lets you start simultaneous blur Auto bidders for a list of collections from a single click. Add the collection addresses to the collectionlist input, with the collections separated with a , and no spaces.
Inputs:
• Collectionlist: You'll launch a blur autobidder automation with each of the collections on this list. Add collection addresses separated with a , without spaces. e.g.
Collection: The bot will place collection bids on this collection
Wallet: Your bids will be placed from this wallet.
Maxbid: The absolute maximum the bot will bid. If the top bid + out bid by is more than this value the bot will not bid.
Undercutby: The bot will undercut the top bid by this amount
8. Alert when x% of a wallet group buys a token
This automation will send you an alert when a number of wallets from a list buys a token. This automation will also trigger for wallets receiving the tokens for free. Useful for monitoring profitable traders/members of an alpha group acquiring tokens in unison.
In this automation you'll have to add the inputs in the Trigger details, advanced:
Min. triggers to run: this will specify how many wallets from your wallet group have to purchase a token from a collection for the trigger to activate. e.g. if you have a a wallet group with 10 wallets and set 5 as Min. triggers to run, then if 5 of the wallets buy/receive a token within 48 hours of each other then the trigger will activate.
To use this automation you need to create a wallet group by looking up wallets in the Compass general search and clicking add to group. Then you need to add the wallet group to the trigger conditions of this automation.
