Updated: 2026-02-20
Crypto journals break when they ignore the fields that actually move your PnL: funding rates, maker/taker fees, leverage drift, and liquidation proximity. This guide shows you exactly what to track for spot and perpetual futures, how to run a weekly review loop, and how to turn journal data into enforceable constraints.
Most crypto journals are stock market journals with a different logo. They track entry, exit, and PnL — and ignore the fields that actually separate profitable crypto traders from everyone else.
In perpetual futures, funding rates can turn a winning directional trade into a net loss. On a 10x leveraged long held for three days during positive funding, the cumulative cost can exceed your edge. If your journal does not log funding, you cannot see it.
Fees are the second silent killer. A trader executing 20 round-trips per week at 0.06% taker fees is paying 2.4% of notional per week. That is not a rounding error. That is a strategy constraint.
The fix is not to log more. The fix is to log the right fields and review them in a loop that produces enforceable changes. That is what this guide builds.
A crypto journal needs two schemas: one for spot and one for perpetual futures. They share a base, but perps require fields that do not exist in spot trading.
The spot schema covers: pair, direction, entry price, exit price, position size (in base and quote), fee tier, fee paid, setup tag, behavior tag, planned stop, and planned R. This is enough for weekly review slicing.
The perps schema adds: leverage (effective, not just the multiplier), margin type (isolated or cross), liquidation price at entry, distance-to-liquidation percentage, cumulative funding paid or received, and funding rate at entry. Without these, you cannot diagnose why a trade that was 'right on direction' still lost money.
If you trade both spot and perps, keep them in the same journal but tag the instrument type. Your weekly review should be able to filter by market type so you can compare execution quality across venues.
Fees and funding are not overhead. They are strategy variables. A journal that ignores them is like a P&L statement that forgets cost of goods sold.
Log fees in basis points per trade, not just the dollar amount. Basis points let you compare execution cost across different position sizes. A 5 bps maker fill on a $50k position is $25. Do that 100 times a month and you have paid $2,500 in fees alone.
Funding rates on perpetual futures are charged every 8 hours (on most exchanges). When markets are bullish and longs are crowded, funding goes positive — meaning longs pay shorts. If you hold a 10x leveraged long through three funding intervals at 0.03%, you have paid 0.9% of notional in funding. On 10x leverage, that is 9% of your margin.
Your journal should surface cumulative funding per trade and per week. When you run your weekly review, check whether funding cost exceeds 20% of gross PnL. If it does, your hold time or leverage is too high for the funding environment.
Leverage is not a number you set and forget. Effective leverage changes as your position moves. Your journal should log both the initial leverage setting and the effective leverage at key points during the trade.
Liquidation distance is the percentage move against you that triggers forced closure. On 10x isolated margin, that distance is roughly 10% (minus fees). On 25x, it is roughly 4%. Logging this number at entry forces you to confront whether the trade has room to breathe.
If your journal shows that most of your stopped-out perps trades had liquidation distance below 8%, you have found a leak. The fix is mechanical: cap leverage or widen stops. You do not need to meditate on it. You need a constraint.
Cross margin is especially dangerous to journal lazily. Because cross margin shares collateral across positions, your liquidation price moves when you open new trades. Log the effective liquidation distance after each new position opens, not just at the first entry.
Raw PnL is misleading in crypto because leverage distorts the numbers. A $500 gain on a 1x spot trade is not the same quality as a $500 gain on a 20x perps trade with a $50 stop. R multiples solve this.
R = (realized PnL) / (planned risk per trade). If you risked $200 and made $600, that is +3R. If you risked $200 and lost $200, that is -1R. Simple. Comparable. Leverage-neutral.
When you normalize to R, your weekly review becomes honest. You can compare a week of spot trades against a week of perps trades because R strips out the leverage amplification and exposes edge quality.
The key detail: use your planned risk for R, not your realized risk. If you moved your stop and lost more than planned, log both the planned R and the realized R. The difference between them is execution slippage — and it is usually a leak.
A journal without a review loop is a diary. It might feel good to write, but it does not change behavior. The review is where your journal earns its keep.
Set a weekly appointment: 45-60 minutes, same day each week. Pull the last 7 days. Slice by setup, session (Asian/London/NY for crypto, or time-of-day for 24/7 markets), and behavior tag.
Find two things: the cohort where you performed best (your edge) and the cohort where you bled the most (your leak). Write them down in one sentence each. If you cannot state them simply, you are not done reviewing.
Then ship one constraint. A constraint is a rule you can enforce on your worst day: max 3 trades per session, no perps above 5x leverage during funding spikes, mandatory 20-minute cooldown after any liquidation. One rule. Measure it next week.
Logging too much. If your journal takes 10 minutes per trade to fill out, you will stop filling it out. Optimize for speed: the critical fields are entry, exit, size, fees, funding (perps), leverage (perps), setup tag, behavior tag, and planned stop. Everything else is optional.
Ignoring funding rates. Traders who hold leveraged positions overnight without logging funding are flying blind. A trade can be correct on direction and still lose money because funding ate the edge.
Using raw PnL instead of R. Dollar PnL mixes edge quality with sizing decisions. R separates them. Without R, your reviews will keep blaming 'bad luck' instead of finding the actual leak.
Skipping the review. The journal is not the product. The weekly review is the product. If you log every trade perfectly but never review, you have built a monument to data entry. The constraint you ship each week is the only output that matters.
Tiltless connects directly to your exchange via API — Binance, Bybit, OKX, Bitget, and more. Fills, fees, and funding are imported automatically so you never have to log them manually.
For perpetual futures trades, Tiltless captures leverage, liquidation price, and cumulative funding per position. These fields are computed from raw fill data, not estimates.
In your weekly review, Tiltless slices trades by the tags you define — setup, session, behavior state — and surfaces the cohort that explains the most damage. You add the tags, Tiltless runs the math.
The output is always the same: one edge, one leak, one constraint. That is the feedback loop that turns a crypto journal from a log into a performance system.
For spot: pair, entry/exit, size, fees, setup tag, behavior tag, and planned stop. For perpetual futures: add leverage, margin type, liquidation price, distance-to-liquidation, and cumulative funding. Tag every trade with your mental state at entry.
Funding is charged every 8 hours on most perpetual futures exchanges. When longs are crowded, funding goes positive and longs pay shorts. On a 10x leveraged position held through three intervals at 0.03%, you pay 0.9% of notional — or 9% of margin. Log it so your review can surface trades where funding erased the edge.
Keep them in the same journal but tag the instrument type. Use different schemas (perps adds leverage, funding, and liquidation fields). Your weekly review should filter by market type so you can compare execution quality across both.
Weekly. Set a 45-60 minute session on the same day each week. Pull the last 7 days, slice by setup, session, and behavior tag, and ship one constraint to enforce next week. Monthly reviews miss the feedback loop speed that active crypto markets demand.
Ignoring funding rates and fees. A trade can be right on direction and still lose money because funding ate the edge or taker fees compounded across high-frequency entries. Log fees in basis points and funding per position so your review can catch it.
Yes. Tiltless connects to Binance, Bybit, OKX, Bitget, and other exchanges via API. Fills, fees, funding, leverage, and liquidation data are imported automatically, so you only need to add behavior tags and run your weekly review.
Tiltless auto-imports fills, fees, and funding from your exchange. Add behavior tags, run a weekly review, and ship one constraint per week.
