<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Position Sizing Archives - LadyChain</title>
	<atom:link href="https://www.ladyww.net/tag/position-sizing/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.ladyww.net/tag/position-sizing/</link>
	<description>Crypto fees, wallets and offers — checked against the terms page</description>
	<lastBuildDate>Tue, 27 Oct 2026 14:02:24 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>

<image>
	<url>https://www.ladyww.net/wp-content/uploads/2026/10/mark-512-150x150.png</url>
	<title>Position Sizing Archives - LadyChain</title>
	<link>https://www.ladyww.net/tag/position-sizing/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Volume Is Not Liquidity</title>
		<link>https://www.ladyww.net/volume-vs-liquidity/</link>
					<comments>https://www.ladyww.net/volume-vs-liquidity/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Tue, 27 Oct 2026 14:02:24 +0000</pubDate>
				<category><![CDATA[Markets]]></category>
		<category><![CDATA[Depth]]></category>
		<category><![CDATA[Execution]]></category>
		<category><![CDATA[Liquidity]]></category>
		<category><![CDATA[Market Impact]]></category>
		<category><![CDATA[Market Structure]]></category>
		<category><![CDATA[Order Books]]></category>
		<category><![CDATA[Position Sizing]]></category>
		<category><![CDATA[Slippage]]></category>
		<category><![CDATA[Trading Costs]]></category>
		<category><![CDATA[Trading Volume]]></category>
		<guid isPermaLink="false">https://www.ladyww.net/volume-vs-liquidity/</guid>

					<description><![CDATA[<p>Volume counts how much traded; liquidity describes how much you can trade before the price moves against you. The volume vs liquidity distinction sounds obvious until you size a position, [&#8230;]</p>
<p>The post <a href="https://www.ladyww.net/volume-vs-liquidity/">Volume Is Not Liquidity</a> appeared first on <a href="https://www.ladyww.net">LadyChain</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Volume counts how much traded; liquidity describes how much you can trade before the price moves against you. The volume vs liquidity distinction sounds obvious until you size a position, and that is when it starts costing money.</p>
<p>The volume vs liquidity gap explains why a market can print record volume and still be impossible to exit at scale. Volume is a historical record of completed trades; liquidity is a forward-looking property of the book, the venue and the moment. One is measured after the fact, the other only revealed when you try to use it.</p>
<ul>
<li><strong>Volume is turnover; liquidity is the cost of converting size into cash.</strong> They correlate loosely and diverge violently under stress.</li>
<li><strong>Reported volume can be inflated cheaply.</strong> Market impact cannot.</li>
<li><strong>Liquidity is a distribution, not a number.</strong> Depth near the midpoint says little about what happens three percent away.</li>
<li><strong>Liquidity is highest when you do not need it.</strong> It withdraws precisely during the events that make risk management matter.</li>
</ul>
<h2>What volume measures</h2>
<p>Volume measures the notional or unit value of trades executed in a window. It is a flow: it resets every day and says nothing about what remains afterwards.</p>
<h3>How the number is constructed</h3>
<p>On a centralised venue, volume is the sum of matched fills by the matching engine. On an automated market maker, it is the sum of swaps against a pool, which includes arbitrage and router traffic that never represents a directional opinion. Aggregators often double count when a single order routes across venues.</p>
<p>Because definitions vary, headline volume is comparable only within one venue&#8217;s own series; cross-venue comparisons mix different accounting rules, fee tiers and treatment of wash activity.</p>
<h3>What volume hides</h3>
<p>A high volume print tells you that a lot changed hands. It does not tell you whether the trades were one large seller hitting a deep bid, or thousands of small orders crossing a thin book. Those two sessions can print identical totals and leave completely different books behind.</p>
<p>Volume also says nothing about who was on the other side. When the counterparty is a market maker recycling inventory, volume reflects churn rather than new demand arriving.</p>
<h2>What liquidity actually is</h2>
<p>Liquidity is the ability to execute a given size within a given time at a price close to the current mid. It has at least three dimensions — depth, tightness and resilience — and a market can be strong on one while weak on the others.</p>
<h3>Depth, spread and resilience</h3>
<p>Depth is the size resting at each price level. Spread is the cost of crossing immediately. Resilience is how quickly the book refills after a large trade takes liquidity out. A market with a one-tick spread but no depth behind it is tight, not liquid.</p>
<p>Resilience is the dimension retail dashboards almost never show, and it is the one that matters most for anyone trading size. A book that refills in seconds can absorb repeated hits; a book that stays thin for minutes cannot.</p>
<h3>Market impact</h3>
<p>Market impact is the price change caused by your own order. It grows faster than linearly with size, because each level you consume is worse than the last. Doubling an order typically more than doubles the slippage.</p>
<div class="slv-table not-prose my-6 overflow-x-auto rounded-2xl border border-ink-800/70 bg-ink-900" data-slv-table><table>
<thead>
<tr>
<th>Property</th>
<th>What it describes</th>
<th>How it is observed</th>
</tr>
</thead>
<tbody>
<tr>
<td>Volume</td>
<td>Trades already completed</td>
<td>Exchange reporting, after the fact</td>
</tr>
<tr>
<td>Depth</td>
<td>Size resting at nearby prices</td>
<td>Order book snapshot</td>
</tr>
<tr>
<td>Spread</td>
<td>Cost of an immediate round trip</td>
<td>Best bid and ask</td>
</tr>
<tr>
<td>Resilience</td>
<td>Speed of book recovery</td>
<td>Repeated sampling after large fills</td>
</tr>
<tr>
<td>Impact</td>
<td>Price move caused by your order</td>
<td>Comparison against a pre-trade benchmark</td>
</tr>
</tbody>
</table></div>
<blockquote><p>Volume is the receipt. Liquidity is the exit. A market can hand you a very impressive receipt and still lock the door when you try to leave.</p></blockquote>
<h2>Why volume vs liquidity diverge in crypto</h2>
<p>Volume vs liquidity gaps are wider in crypto than in most traditional markets because the same asset trades across dozens of venues with independent books, and because incentives distort the reported numbers.</p>
<p>Trading competitions and reward programmes pay for volume. The cheapest way to earn them is to trade at minimal cost, which lifts the printed total without adding a unit of usable depth. The practice is discouraged on most venues and detected on some, but the incentive is durable.</p>
<p>Fragmentation works the other way. Liquidity that looks deep on one exchange may be the same market maker quoting on five others, all cancelling together when volatility rises. Aggregate depth across venues is therefore systematically overstated, sometimes dramatically.</p>
<p>Token design adds a third source of divergence. A pair with high nominal volume can sit in a pool whose depth is concentrated in a narrow band, so a modest sell moves price far more than the volume figure implies.</p>
<h2>Estimating real liquidity before you trade</h2>
<p>The practical response is to measure the thing you actually care about — the cost of your own size — rather than the thing that is easy to display.</p>
<ol>
<li>Take repeated order book snapshots across several hours, not one screenshot at a quiet moment.</li>
<li>Walk the book for your intended size and record the volume-weighted average price you would pay.</li>
<li>Subtract the mid to get slippage in basis points; do this at two or three sizes to see how impact scales.</li>
<li>Compare the result with the quoted spread and with the 24-hour volume figure to see whether the venue&#8217;s headline matches its depth.</li>
<li>Repeat the exercise at a high-volatility moment; the difference between the two readings is your realistic liquidity stress estimate.</li>
<li>Add fees, funding and withdrawal costs to the slippage figure to get a full round-trip cost.</li>
<li>Size the position so that expected edge exceeds that total cost by a margin you are comfortable defending.</li>
</ol>
<p>A worked version: if walking the book for 250,000 units fills at 40 basis points above the mid, the immediate cost is 0.40 percent, or 1,000 units. If the thesis needs a 2 percent move to pay, a fifth of the gain is spent before the position exists — and exiting at a similar cost doubles that.</p>
<h2>Where volume vs liquidity analysis fails</h2>
<p>Liquidity is not a constant that occasionally dips. It is a regime variable that changes with volatility, with funding, and with the health of the market makers supplying it.</p>
<p><strong>Withdrawal.</strong> Quoters pull when inventory risk rises. The book does not thin gradually; it gaps. Stops placed just beyond the visible depth are the first thing to be triggered by the resulting wick.</p>
<p><strong>Crowded exits.</strong> Positions built on the assumption of liquid exits are, by construction, the same positions that need to exit together. When everyone measures liquidity at the same calm moment, the stress estimate is wrong for everyone simultaneously.</p>
<p><strong>Venue-specific outages.</strong> During congestion, one venue may stop matching while others keep trading. Prices diverge, and any strategy that assumes a single unified price temporarily breaks.</p>
<p><strong>Hidden size.</strong> Iceberg orders and dark liquidity mean the visible book understates what is available — but only for patient execution. It does not help if you need to be out in thirty seconds.</p>
<p>The mitigation is procedural: cap size as a fraction of measured depth rather than of volume, spread execution over time, and assume the stress estimate is optimistic by some factor you choose in advance.</p>
<p>The post <a href="https://www.ladyww.net/volume-vs-liquidity/">Volume Is Not Liquidity</a> appeared first on <a href="https://www.ladyww.net">LadyChain</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.ladyww.net/volume-vs-liquidity/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Volatility Regimes: Why Your Strategy Stops Working</title>
		<link>https://www.ladyww.net/volatility-regimes/</link>
					<comments>https://www.ladyww.net/volatility-regimes/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Tue, 27 Oct 2026 12:02:25 +0000</pubDate>
				<category><![CDATA[Markets]]></category>
		<category><![CDATA[Backtesting]]></category>
		<category><![CDATA[Execution Costs]]></category>
		<category><![CDATA[Implied Volatility]]></category>
		<category><![CDATA[Liquidity]]></category>
		<category><![CDATA[Market Regimes]]></category>
		<category><![CDATA[Position Sizing]]></category>
		<category><![CDATA[Realized Volatility]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[Strategy Design]]></category>
		<category><![CDATA[Volatility Regime]]></category>
		<guid isPermaLink="false">https://www.ladyww.net/volatility-regimes/</guid>

					<description><![CDATA[<p>A volatility regime is a persistent state in which the market&#8217;s typical move size, and the way it responds to news, stays broadly the same. Within a regime, returns look [&#8230;]</p>
<p>The post <a href="https://www.ladyww.net/volatility-regimes/">Volatility Regimes: Why Your Strategy Stops Working</a> appeared first on <a href="https://www.ladyww.net">LadyChain</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>A volatility regime is a persistent state in which the market&#8217;s typical move size, and the way it responds to news, stays broadly the same. Within a regime, returns look roughly stationary; across regimes, they do not.</p>
<p>Strategies are implicitly calibrated to one volatility regime, even when nobody writes that assumption down. A parameter set tuned on quiet months encodes the cost structure of quiet months — tight spreads, shallow pullbacks, orderly liquidations — and that cost structure is the first thing to change when the regime shifts.</p>
<ul>
<li><strong>Regimes are persistent, not permanent.</strong> They last weeks to months, which is long enough to be mistaken for the normal state of the market.</li>
<li><strong>Volatility clusters.</strong> Large moves follow large moves, so the regime you observe today is the best available guess for tomorrow.</li>
<li><strong>Strategy decay is usually a cost problem, not a signal problem.</strong> Spreads widen, slippage grows and stops get hit by noise rather than by thesis.</li>
<li><strong>Detection lags.</strong> Every filter that identifies a regime change confirms it after the fact, and the lag is where the damage happens.</li>
</ul>
<h2>What a volatility regime consists of</h2>
<p>A regime is defined by more than the level of volatility. It also includes the asymmetry between up and down moves, the speed of mean reversion, and how liquidity behaves when price moves quickly.</p>
<h3>Realized and implied</h3>
<p>Realized volatility is computed from past returns and is always backward-looking. Implied volatility is priced into options and is forward-looking, but only for the horizon the contract covers and only as far as the options market is deep enough to be informative.</p>
<p>The gap between the two is itself regime-dependent. In calm periods implied tends to sit above realized, because sellers of optionality demand compensation for tail risk. In stressed periods that relationship can invert sharply, and the inversion is usually a better signal of regime change than either series alone.</p>
<h3>How regimes are identified in practice</h3>
<p>Most detection methods reduce to comparing a short-window estimate with a long-window distribution. A common approach ranks the last ten days of realized volatility against the trailing year; readings above the eightieth percentile are treated as high-volatility, below the twentieth as low.</p>
<p>Hidden Markov models and change-point detection respond faster but are harder to audit, and auditability matters more than elegance when the output changes position size.</p>
<h2>Why a volatility regime breaks a strategy</h2>
<p>A strategy breaks when the distribution it was fitted to stops describing the data, and the break usually shows up in execution costs before it shows up in signal quality.</p>
<h3>Stops and position sizing</h3>
<p>A stop placed at twice the average true range is meaningful in a low-volatility regime and meaningless in a high one, where ordinary noise exceeds it. The strategy does not become wrong; it becomes a machine for paying the spread.</p>
<p>Position sizing has the same problem in reverse. Sizing by fixed notional leaves risk exposure rising with volatility; sizing by volatility target keeps risk constant but forces selling into strength and buying into weakness, which has its own cost in a trending market.</p>
<h3>Correlation and liquidity</h3>
<p>In stress, correlations converge toward one. Diversification that looked robust in a calm regime provides less protection exactly when it is needed, so portfolio-level volatility rises faster than any single-asset estimate suggests.</p>
<p>Liquidity withdraws at the same time. Market makers widen and thin their quotes, impact per unit traded rises, and a strategy that assumed it could exit at the mid now pays several basis points for the privilege.</p>
<div class="slv-table not-prose my-6 overflow-x-auto rounded-2xl border border-ink-800/70 bg-ink-900" data-slv-table><table>
<thead>
<tr>
<th>Feature</th>
<th>Low-volatility regime</th>
<th>High-volatility regime</th>
</tr>
</thead>
<tbody>
<tr>
<td>Realized volatility</td>
<td>Below the 20th percentile</td>
<td>Above the 80th percentile</td>
</tr>
<tr>
<td>Spread and depth</td>
<td>Tight, deep, resilient</td>
<td>Wide, thin, slow to refill</td>
</tr>
<tr>
<td>Cross-asset correlation</td>
<td>Dispersed</td>
<td>Compressed toward one</td>
</tr>
<tr>
<td>Funding and carry</td>
<td>Stable, small</td>
<td>Volatile, often extreme</td>
</tr>
<tr>
<td>Liquidation clustering</td>
<td>Isolated</td>
<td>Cascading</td>
</tr>
<tr>
<td>Mean reversion</td>
<td>Works within a range</td>
<td>Breaks, then overshoots</td>
</tr>
</tbody>
</table></div>
<blockquote><p>A strategy is not a set of rules. It is a set of rules plus an assumption about what execution costs, and the assumption is what the volatility regime rewrites.</p></blockquote>
<h2>Identifying the regime you are in</h2>
<p>Regime identification is a measurement problem, and it is worth building the measurement before building the strategy that depends on it.</p>
<ol>
<li>Compute daily realized volatility from close-to-close returns over a short window, typically ten to twenty days.</li>
<li>Build a trailing reference distribution, usually one year, and convert the current reading into a percentile.</li>
<li>Add a second, slower measure over sixty to ninety days to distinguish a genuine shift from a single noisy week.</li>
<li>Track execution cost separately: median spread, depth at five levels, and average slippage on your own fills.</li>
<li>Compare the two. A volatility shift without a cost shift usually means the move is orderly; both moving together means the regime has changed.</li>
<li>Define thresholds in advance — for example, act only when the fast percentile and the cost measure agree for five consecutive sessions.</li>
<li>Record the regime label alongside every trade so that performance can later be split by state rather than averaged across all of them.</li>
</ol>
<p>A worked illustration: suppose a mean-reversion strategy earns 0.30 percent per round trip in a calm regime with 12 basis points of total cost. In a high-volatility regime the same signal frequency holds but cost rises to 35 basis points. Net edge falls from 18 to −5 basis points, and the strategy flips from profitable to loss-making without any change to its logic. The break is arithmetic, not mystical.</p>
<h2>The transition problem</h2>
<p>Most losses from regime shifts occur in the transition, not in the new state. By the time a regime is unambiguous, the market has already repriced the cost of being wrong.</p>
<p>Filters that require confirmation are slow by construction. A rule that waits for five sessions above the eightieth percentile will enter the high-volatility state roughly a week late, which is often after the largest single move has already happened.</p>
<p>Filters that react quickly produce false positives. A single liquidation cascade can push a fast percentile to an extreme for two days and then revert, and a strategy that de-risks on every spike will spend its budget on transaction costs rather than on protection.</p>
<p>The practical compromise is asymmetric: de-risk quickly, re-risk slowly. Adding exposure is cheap in expectation when you are wrong; carrying too much exposure through a genuine shift is not.</p>
<h2>Adapting without overfitting</h2>
<p>Adaptation should change a small number of parameters, chosen because they have a mechanical link to volatility, rather than a large number chosen because they improved a backtest.</p>
<p>Volatility-scaled position size, wider stops expressed in volatility units, and lower gross exposure in the top volatility bucket are defensible because each one responds to a real cost. Adding a new indicator, a new lookback and a new threshold at the same time is not adaptation; it is fitting noise with extra steps.</p>
<p>Separate the two failure modes explicitly. If a strategy stops working because the signal decayed, changing position size will not fix it. If it stops working because costs doubled, changing the signal will not fix it either. The regime label tells you which of the two you are looking at, provided you recorded costs as carefully as you recorded returns.</p>
<p>The post <a href="https://www.ladyww.net/volatility-regimes/">Volatility Regimes: Why Your Strategy Stops Working</a> appeared first on <a href="https://www.ladyww.net">LadyChain</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.ladyww.net/volatility-regimes/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
