Atlas Sbw870763c

Coinrule Help Center

When using the "anycoin" scanner,  multiple assets may be selected. Coins are dynamically sorted depending on indicator and operation. Usually, the first condition before the action that is evaluated as TRUE sorts the entire block:​

Rule starts at 10:00pm and conditions are evaluated

BTC, ETH, LTC and 10 other coins have met the 3 conditions set in the above screenshot

 to be evaluated as TRUE sorts the entire block that is before the action. That is, 'MA9 crossing above price'

The rule engine will sort the 13 coins by MA9 in descending order, which means it will select the coin with the highest MA9 first and keep sorting in descending order

For example, if BTC has the highest MA9 increase, it will be bought first. Then if ETH has the second highest MA9 increase it will be bought second and so on

Important note: Coins are sorted in descending order for 'Crossing above', 'Increased by' and 'Greater than' conditions as the scanner sorts according to the biggest value.

BTC, ETH, LTC and 10 other coins have all met the BUY conditions

 before the action that is evaluated as TRUE sorts the entire block that is before the action. That is, 'MA9 crossing below price'

The rule engine will sort the 13 coins by MA9 in ascending order, which means it will select the coin with the lowest MA9 first and keep sorting in ascending order

For example, if BTC has the lowest MA9 increase, it will be bought first. Then if ETH has the second lowest MA9 increase it will be bought next and so on

Important note: Coins are sorted in ascending order for 'Crossing below', 'Decreased by' and 'Lower than' conditions as the scanner sorts according to the lowest number.

Additionally, coins are sorted by absolute value in 'Crossing Above/Below' & 'Lower/Greater than' events. 

However in cases of increase/decrease, coins are sorted based on percentage as these conditions are already using percentage growth:

An explanation on how coins are sorted when using the 'any coin' scanner

Coin Sorting Logic

 How To Build 'Complex Rules' On Coinrule

Trading Rules on Coinrule can be powerful and complex at the same time. 

This article runs through some complex rules to lay out how the rule logic works and also covers some common misconceptions. 

Case 1: Condition Block - How the Sell Action will be triggered

For the rule to Sell, the following condition logic must be TRUE: 

Condition 4 above must always be TRUE for the Sell to occur because of the sequential order

Any time you use AND, it relates to ALL previous conditions inside the block. That means that an 'AND' in the condition block, the following condition must be TRUE for the rule to trigger

Only 1 and 2 TRUE: The rule does not sell

just related to 3 but to ALL conditions in this block 

A common misconception is around the grouping of blocks. It is 

Rule previously bought Ethereum with USDT at $3,000

Price decreases 4% from $3,000, RSI is 50

Condition 1 is TRUE, Condition 2 is FALSE, Condition 3 is FALSE, Condition 4 is TRUE: 

Price decreases 2% from $3,000, RSI is 50

Condition 1 is FALSE, Condition 2 is FALSE, Condition 3 is FALSE, Condition 4 is TRUE: 

Condition 1 is FALSE, Condition 2 is FALSE, Condition 3 is TRUE, Condition 4 is FALSE: 

Price increases 5% from $3,000 ($3,150), 

Price increases 7% from $3,000 ($3,210), 

Condition 1 is FALSE, Condition 2 is FALSE, Condition 3 is TRUE, Condition 4 is TRUE: 

Condition 1 is FALSE, Condition 2 is TRUE, Condition 3 is FALSE, Condition 4 is FALSE: 

Price increases 5% ($3,150), then price decreases 2% ($3,087), RSI is 66

Condition 1 is FALSE, Condition 2 is TRUE, Condition 3 is FALSE, Condition 4 is TRUE: 

Case 2: Condition Block - How the Sell Action will be triggered

The difference compared to Case 1 is the 'and' rather than 'or' in Condition 2.

If 3 is FALSE, BOTH 1 AND 2 must be TRUE together with 4 for the rule to sell

Condition 4 must always be TRUE for the rule to sell because of the sequential order

1 is FALSE, 2 is TRUE, 3 is TRUE, 4 is TRUE: 

1 and 2 are TRUE, 3 is FALSE, 4 is TRUE: 

 create a separate group of conditions that have to be TRUE

The OR inside a condition block provides an alternative possible condition for a rule to be met

It should NOT be confused with the OR Operator which 

The recently introduced 'Wait For' operator is a powerful tool to validate a trend.

Here are some examples of how it applies in a complex rule:

Price increases by 1% from $3,000, RSI is 70 in a timeframe of 5 minutes
 


First condition after OR Operator is TRUE

'Wait for' loop starts and waits for 5 minutes

Important to note: once the 'Wait For' loop has been triggered here, Block 1 will no longer be checked

greater than 65 in a timeframe of 15 minutes: Rule 

 than 65 in a timeframe of 15 minutes: Loop restarts the 5 minute wait and then again checks if RSI is greater than 65 on a timeframe of 15 minutes

The 'Wait For' Loop will continue running until the RSI condition is met and will then trigger the following Sell Action

You can also use an OR operator to create two possible Action scenarios.

In the above rule, the first condition will be checked, if the condition is NOT met, the rule will continue by checking the condition after the OR. If the condition after the OR IS met, the rule will trigger. If the condition is NOT met, the rule will continue by checking the first condition.

This enables you to build strategies that would trigger a BUY action and a SELL action based on two different conditions.

Build Advanced Trading Strategies with Coinrule. A Walk-through some commonly asked questions about rule logic

Complex Rules

Introducing: Crossing Events, Closed Candles & Rule Logic

Coinrule uses only confirmed “closed prices” to trigger events. This removes intra-candle volatility and ensures a more accurate signal is used for your strategy.

How would the above rule logic be interpreted: 

The latest closed MA (9) candle value is compared to the close price of the previous closed candle.

Generally, all crossing events (no matter the indicator) are evaluated like this: 

The rule engine will always evaluate the value of price or an indicator of the 'latest closed candle' and compare it to a value, be it price or an indicator, of the previous closed candle.

The rule will trigger immediately with the opening of the new candle.

For the above condition to trigger, the 30 minutes BB Upper Band value in the latest Closed Candle must have crossed above the EMA(55) value. See below for the exact calculation steps:

For the above condition to trigger, the 30 minutes MFI value in the latest Closed Candle must have been lower than 50. See below for the exact calculation steps: 

When dealing with rules (such as the example above) with conditions with multiple timeframes, the rule can trigger at anytime.

, the current price is compared to that close price as quickly as possible, depending on your plan and server speed. The first condition (

IF any coin has price increase by 0.001% within 1 week

 in every moment which would trigger the rule to execute.​

 again if condition 2 is also true again.​

Head to the rule page to build your rule using the crossing logic on 

How are Crossing events calculated/interpreted by the Rule Engine?

Crossing Events, Closed Candles & Rule Logic

How To Use ‘Greater/Lower Than Previous Value’ Of Indicator

Coinrule has introduced a new feature 'greater/lower than previous value'. This update allows you to compare the previous value of an indicator to the current value to trigger events and ensures a more accurate signal is used for your strategy. 

This feature works with Bollinger Bands (BB), Exponential Moving Average (EMA), Moving Average (MA) and Open High Low Close (OHLC) on Coinrule. 

See below for an example on how to incorporate this feature into your strategies:

In the example above, when using ‘EMA (12) greater than previous value of EMA (12)’ the bot compares the value of the most-recent available value of EMA (12) with the previous value of EMA (12).

If your rule features ‘EMA greater than previous value’ condition and specifies a 1-hour timeframe, the rule will use the previous 1 hour EMA close value compared to the current EMA close value as a reference point for the following 1 hour. If at any time, within this timeframe, EMA (12) is greater than the previous value of EMA (12), the rule will execute. This also applies when using “indicator lower than previous value”

Important tip: Coinrule uses only confirmed “closed candles” to trigger events and applies to indicators also. The importance of using closed candles to trigger events is to avoid intra candle volatility and to prevent the rule from triggering false signals.

We hope you enjoy the new feature. Happy trading!

Compare the current value of an indicator to the previous value for more flexibility with indicators

The Volume indicator is based on aggregated volume data across all exchanges for the last 24h as per 

For the above rule example, in every given moment, the volume contains trades from “24h” ago to “current time”. The volume value is updated regularly. The evaluation of the above sequence will be 

if the current volume increases by 5% compared to the volume 24 hours ago.

In the above case, the current volume is compared to the amount ($5 billion) specified in the rule. 

Important note: We are working on improvements to the volume indicator. The new volume indicator will be based on candles for each specific exchange, generally it should be equal to volume seen on TradingView.

How Is the Volume Indicator Calculated?

To read more about Trailing Orders in general and see examples of rule executions, please refer to 

This is the price at which the rule bought or sold a coin 

This is the latest available price at which a coin is trading

The price at which your rule would trigger

The Current Live Price is continuously evaluated against the 'Price at rule launch' until the trailing condition has been met and the rule triggers. The rule triggers when 'Trailing Order Price' = 'Current Live Price'.

At the launch of the rule, the Trailing Order Price is equal to the 'Price at rule launch' minus 1% as per the condition set above ('if that coin has price decrease by 1% trailing'). As soon as the Current Live Price starts to change over time as the rule continues to run, the Trailing Order Price can be calculated as follows: 'Current Live Price minus 1%'.

Rule buys 15 USD of ETH with BUSD at 4.15pm at 1 ETH = 1,000 USD

At 4.15pm, 'Price at rule launch' is 1,000 USD, the Trailing Order Price is 1,000 USD - 1% = 990 USD

Assuming the Current Live Price of ETH at 10.20pm is now 1,110 USD, the order would trigger at the Trailing Order Price of 1,110 USD - 1% = 1,098.9 USD

In the example above, there are multiple conditions that need to be met before the order executes. To activate trailing:

 the arbiter validates both conditions in the i.e.

IF that coin has price increase by 3 % from price at which you bought AND IF that coin has price decrease by 1 % trailing

if both conditions are true, the output will be true and the 

If one condition is true and the other condition is false, the output will be false and the

 be triggered. Instead, another validation will be carried out by the arbiter continuously until 

Rule Logic Example 3a - Trailing in first Condition (decrease by)

1) Price decreases until it has decreased by 10% from $1,197 (trailing order price) --> the rule triggers

2) Price increases from $1,197, then at some point decreases by 10%

Example: assuming the price increases to $1,400 - this now becomes the new trailing order price. The rule triggers if the price decreases by 10% from $1,400. 

Assuming the price now drops 10% from $1,400, reaching $1,260, the rule will sell.

The difference between using the 'Current Live Price' option in the dropdown [referred to here as 'price at rule launch'] and the 'trailing' price is that the rule would have continued to evaluate the price increase against the 'price at rule launch' of $1,197 if 'trailing' was not used. The rule would have triggered at a lower price of $1,077. The trader would have done worse compared to selling at $1,260.

Coinrule's engine will always take the highest reached trailing order price from which to calculate the trailing decrease.

Rule Logic Example 3b - Trailing in first Condition (increase by)

1) Price increases until it has increased by 10% from $1,203 (trailing order price) --> the rule triggers

Let's assume the price of 1 ETH now decreases to $1,150. The Trailing Order Price gets updated to $1,150. The system now evaluates the condition

against the new Trailing Order Price of $1,150. 

For the rule to trigger, the price would now need to increase by 10% from 

 and reach a price of $1,300 before the order triggers.  

Without using the trailing functionality here, the rule would have triggered at a higher price of $1,323.

In connection with a 'trailing price increase' and a 'Buy' you can catch trend reversals with a better entry price compared to the regular 'current live price' value. 

Read how we calculate price values for Trailing Buys/Sells on Coinrule

Trailing Order Logic

  Understanding: ‘Within’, Closed Candles and Price

For the above condition to trigger, the price increase by 5% 'WITHIN 15 minutes' would have to happen within one 15 minute candle.

Rule starts at 10.03pm, price for 1 ETH is 1,000 USD

The last Close Price of the last closed 15 minutes candle (9.45pm) is 995 USD

The condition is not met. The condition looks for a 5% increase 

Let's assume at 10.13pm the price of 1 ETH reaches 1,045 USD (straight from 995 USD). 

The condition of a 5% increase is met and the rule 

Let's assume it is 10.37pm, the price of 1 ETH is 1,020, the 10.15pm Close Price of the 15 minute Candle was 1,010 USD. The condition now looks for a 5% price increase against the 1,010 USD. 

The rule would trigger if the price were to reach 1,060.5 USD which is a 5% increase.

'Within x time period' calculation and closed candles

‘Within’, Closed Candles and Price

 FAQ: Price Increase With Multiple Coins Logic

When using price increase by x% with multiple assets, the snapshot of coins are taken at the start of the rule and updated once the rule's conditions are met by one of the selected coins:

Rule starts at 8pm and conditions are evaluated

Current live price snapshot of referenced coins (ADADOWN, ADA, ACM) is taken

ADA Price was 0.3 USD then price increased by 1%. 

Once the rule buys ADA we update the snapshot for all the coins (ADADOWN, ADA & ACM)

The rule continues to evaluate the conditions using the updated snapshot of the coins

CurrentLivePrice snapshot is taken at the beginning of every cycle

Understand how price increase working with multiple coins

Price Increase With Multiple Coins Logic

We understand that, in the world of trading, time is of the essence. The enhanced 

 improvements are designed to ensure your trading rules keep running, even when unforeseen errors crop up. Instead of stopping entirely upon encountering an error, your rule will attempt to recover and continue to execute. ​

Our main goal is to minimize interruptions and ensure a smooth trading experience for you.

Once an error occurs in a rule, here's a breakdown of the rule persistence logic:  

: If the rule faces consistent errors, it will pause for 

: After the brief pause, the rule will retry 

: If still unsuccessful, it will pause for 

: Following persistent errors, the rule will pause for

: If unsuccessful, the rule will pause for 

: If all these attempts fail, the rule will then be paused and no retry attempts will be made.

By following this structure, we are maximizing the chances of your rule executing successfully, while also ensuring it doesn't get stuck in a continuous loop of errors.

We'd like to highlight that the Rule Persistence feature is not fully compatible with 'any time' rules as of now. Our team is aware of this limitation and is diligently working to introduce further improvements to address this in the near future.

The enhanced Rule Persistence feature is a testament to Coinrule's commitment to providing a seamless and reliable trading platform for its users. We're constantly listening to feedback and improving. If you have any questions or face issues, please don't hesitate to reach out to our support team via 

Stay tuned for more updates and happy trading!

Breakdown of rule persistence logic to ensure rules keep running even when errors occur

Rule Persistence Logic

 Understand Automatic Flipping Protection for Leverage Rules

Our system checks if your open/short positions that were opened by Coinrule are still open before placing trades. In the past, a position opened by a Coinrule rule that was manually closed by you on an exchange would have been considered still open by the rule. Our system, unaware of this closure, might inadvertently open a short or long position. For instance, if it was originally a long position which got liquidated, the rule could have opened a new short position. Now, if the position is found to be non-existent, the rule engine will terminate the position on our end. Consequently, users will receive a notification reading "Position externally closed" (refer to image below).

If you close a position outside of Coinrule, the system takes it into account

Automatic Flipping Protection for Leverage Rules

Creating rules based on the comparison of candlestick data is a powerful method to automate trading strategies on Coinrule. We have now launched support for comparing previous values of a candle when using 

, giving you even more customizability for your strategies!

For instance, a user can create a rule with the above condition, comparing candle values. This condition leverages the momentum by identifying an uptrend and taking a position to benefit from the potential rise.

The rule engine compares the current closing price to the previous close value of a coin to determine whether the set condition is met. If the current close is higher than the previous, indicating an upward trend, the rule triggers a buy order.

Moreover, traders are not limited to comparing just closing prices. The platform allows for the comparison of other vital data points, such as:

: The highest price reached during the candle's timeframe.

: The lowest price within the candle's timeframe.

: The closing price at the end of the candle's timeframe.

By setting up rules that compare these values to their previous instances, users can choose to look for a close value 

This feature's flexibility ensures that users can develop complex strategies that can automatically react to market changes, potentially increasing their chances of making profitable trades.

When implementing this strategy, users should consider the following steps:

1. Select "any coin", specific coin(s) or a preferred basket.

: Decide which candlestick data point (open, high, low, or close) you want to compare.

: Specify whether the rule should trigger when the price is 

: Establish the period for comparison, like 4 hours or any other preferred timeframe.

: Decide on the action to be executed once the condition is met, such as buying or selling a percentage of the chosen coin.

A guide to comparing the previous value of a candle's open, high, low or closed price

Comparing Candles

Coinrule's speed depends on two factors: condition evaluation and order placement. While order placement usually happens in <1 second speeds and depends also on Exchange APIs, Coinrule is working hard to speed up condition evaluation processes wherever possible.

To understand condition evaluation, it's essential to understand how frequently the system scans for triggers. This frequency varies depending on the subscription plan and can significantly impact the responsiveness of your trading strategies. Here's a breakdown of the rule scan frequencies for each plan.

The Starter Plan (also the free plan) offers a solid foundation for those new to automated trading. Under this plan, the system scans for triggers 

 This frequency is adequate for strategies that don't require rapid response to market changes, making it an excellent choice for beginners or those with a more long-term trading approach.

For more active traders, the Investor/Trader Plan offers a higher frequency. The system scans for triggers 

. This increased frequency allows for more timely reactions to market changes, making it suitable for those who engage in more frequent trading or those who require a quicker response to market volatility.

The Fund Plan is designed for the most demanding traders who require the quickest response times. Under this plan, the system scans for triggers 

. This near-instantaneous scanning ensures that your trading strategies can react almost immediately to market movements, offering a significant advantage in fast-paced trading environments.

The frequency with which Coinrule scans for triggers is tailored to suit various trading styles and needs. Whether you're starting out, trading more frequently, or need rapid response times, there's a plan that fits your requirements. Understanding this aspect of Coinrule's functionality helps in optimizing your trading strategies for better performance.

How fast is Coinrule?

This feature allows users to fine tune their automated trading strategies by setting a specific frequency limit on their buy orders. When using 'not more than once per x', the rule engine ensures that the first action, which opens a position, is executed no more than once within the designated timeframe. 

As mentioned above, 'Not more than once per x' feature 

 (in the first block), meaning when opening the position. The reason behind this is explained below:

the exit condition(s) are designed to trigger as soon as they are met - any unintended limitation could cause much bigger damage; and

it's next to "execute X times" - that also does not mean there will be 500 trades in total. It means the rule will open a position 500 times, that is 1,000 trades (buying and selling).

This article explains how the 'no more than once per x' feature works

Technical FAQ