BTC Cycle Toolkit v1.1.1 (EN) | by Nickxs91

Short Description:

A long-term Bitcoin cycle toolkit built around Halvings: historical top/low anchors, current-cycle candidate/lock logic, laddered buy/sell levels with backtesting — plus a Daily-based Pi Cycle Top signal as an optional additional criterion.



Full Description:
What is this?

This script is designed primarily as a Bitcoin cycle visualization & planning toolkit based on Halvings (4-year cycle thesis).
It helps you build a structured plan for buying and selling over time depending on where price might be positioned inside the cycle.

What you get on the chart

Halving markers (vertical lines) + optional labels, countdown and reminders

Fixed historical cycle tops & lows as horizontal reference anchors (~rounded values)

Current cycle (post Halving 2024) auto-detection:

Top candidate (High-since-Halving or Pivot-based)

Robust lock logic for top and low (prevents locking too early)

Candidate vs Locked displayed clearly

Buy/Sell ladder levels

3–10 levels, fully adjustable ranges (drawdown zone / growth zone)

Linear or exponential sizing (“the deeper, the more” / “the higher, the more”)

Labels show price and allocation (optionally estimated amount)

Backtesting strategy

Auto multi-cycle mode or manual single-cycle segments

Optional “institutional-style” filters (trend/RSI/volume)

Pi Cycle Top (Daily-based)

Stable across all timeframes (computed on Daily)

Optional: if Pi triggers, sell the remaining position (“Exit All”)



Important note about Pi Cycle Top

The Pi Cycle Top indicator can be very accurate when it triggers, but it does not trigger in every cycle.
I personally treat it as an additional criterion, not the only definition of a cycle top.

Who is this for?

Long-term BTC investors who think in cycles

Traders/investors who prefer laddered entries/exits instead of all-in/all-out

Anyone who wants a structured way to “map” price behavior around Halvings



Disclaimer

This is a research/visualization tool — not financial advice.
Markets evolve; historical cycles are not guarantees. Backtest results are approximations and include conservative costs.



Roadmap

I plan to continue improving features based on feedback. Suggestions are welcome.
Nice to know: There is a German version (private).



How to use (Quick workflow)

1. Use 1D timeframe for the cleanest cycle context
   
3. Keep preset Conservative (release default) or Custom for own preferences.
   
5. Enable Halvings + historical anchors
   
7. Choose auto method (Pivot = more stable, HighSinceHalving = faster)
   
9. Set level count & ranges (e.g., 7 levels)
   
11. Backtest via Auto Multi-Cycle or Manual segment
    
13. Optional: enable Pi Cycle “Exit All” as an extra top-risk reduction layer