<?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>Risk Management Archives - LadyChain</title>
	<atom:link href="https://www.ladyww.net/tag/risk-management/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.ladyww.net/tag/risk-management/</link>
	<description>Crypto fees, wallets and offers — checked against the terms page</description>
	<lastBuildDate>Tue, 27 Oct 2026 16:02:29 +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>Risk Management Archives - LadyChain</title>
	<link>https://www.ladyww.net/tag/risk-management/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Liquidation Cascades: How One Position Takes Out Ten</title>
		<link>https://www.ladyww.net/liquidation-cascades/</link>
					<comments>https://www.ladyww.net/liquidation-cascades/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Tue, 27 Oct 2026 16:02:29 +0000</pubDate>
				<category><![CDATA[Markets]]></category>
		<category><![CDATA[Auto-Deleveraging]]></category>
		<category><![CDATA[Derivatives]]></category>
		<category><![CDATA[Leverage]]></category>
		<category><![CDATA[Liquidation Cascade]]></category>
		<category><![CDATA[Margin]]></category>
		<category><![CDATA[Market Microstructure]]></category>
		<category><![CDATA[Order Book Depth]]></category>
		<category><![CDATA[Perpetual Futures]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[Volatility]]></category>
		<guid isPermaLink="false">https://www.ladyww.net/liquidation-cascades/</guid>

					<description><![CDATA[<p>A liquidation cascade is what happens when forced selling creates the price move that triggers the next round of forced selling. The mechanism is unglamorous: a leveraged position falls below [&#8230;]</p>
<p>The post <a href="https://www.ladyww.net/liquidation-cascades/">Liquidation Cascades: How One Position Takes Out Ten</a> appeared first on <a href="https://www.ladyww.net">LadyChain</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>A liquidation cascade is what happens when forced selling creates the price move that triggers the next round of forced selling. The mechanism is unglamorous: a leveraged position falls below the maintenance requirement its venue sets, the venue closes it at market, that order moves the price, and the move pushes the next position past its own threshold. A liquidation cascade is therefore not a single event but a feedback loop with a duration — sometimes seconds, sometimes most of a trading day.</p>
<p>Most explanations stop at &#8220;leverage is risky&#8221; and move on. That is not actionable. What matters is the transmission path between one trader&#8217;s forced exit and a hundred unrelated balances, because that path decides which of your positions are actually exposed, how quickly a venue passes the shock along, and why the printed low often sits well below the level where the original seller was simply wrong.</p>
<ul>
<li><strong>A cascade is a liquidity problem first, a leverage problem second.</strong> Leverage sets the trigger; available depth decides how far each trigger moves the price.</li>
<li><strong>The dangerous zone is where thresholds cluster.</strong> Round numbers and popular entry levels concentrate stops and liquidation prices inside the same few percent of price.</li>
<li><strong>Venue design changes the transmission speed.</strong> Insurance funds, auto-deleveraging and partial liquidation rules decide whether the loop damps or accelerates.</li>
<li><strong>You cannot opt out, only reduce exposure.</strong> Holding spot removes your own threshold, not the price impact of everyone else&#8217;s.</li>
</ul>
<h2>How a liquidation cascade starts</h2>
<p>A cascade starts when the gap between the current price and a large cluster of liquidation thresholds is smaller than ordinary volatility. Nothing abnormal needs to happen: a quiet market with crowded positioning is enough. The first break is usually small, and it is the response to that break — not the break itself — that decides the outcome.</p>
<p>Liquidation engines do not wait for a limit price. Once a position sits under its maintenance requirement, the venue typically submits market orders for the size it needs to close, so the exit price is whatever the book offers at that moment. In a thin book the fill is bad, the remaining collateral is consumed, and every neighbouring position with a similar threshold is now underwater too.</p>
<h3>Isolated margin versus cross margin</h3>
<p>Isolated margin caps the damage at one position&#8217;s collateral. The position dies, the rest of the account survives, and the venue&#8217;s exposure is bounded. Cross margin behaves differently: every asset in the account backs every position, so one losing leg can consume collateral that was notionally supporting the others. Cross margin is more capital-efficient in calm markets and transmits losses further in fast ones. Neither is safer in the abstract; they fail at different speeds.</p>
<h3>Why the order book matters more than the leverage number</h3>
<p>Two traders can run the same leverage with wildly different risk. The one whose position is small relative to nearby depth gets closed near the threshold. The one whose position is large relative to that depth gets closed far below it, dragging price through other people&#8217;s thresholds on the way out. Depth is the variable that converts a liquidation into a liquidation cascade.</p>
<h2>The three amplifiers that turn a dip into a liquidation cascade</h2>
<p>Three structural features decide whether a break stays local or goes systemic: stop clustering, venue backstops, and the funding response that follows.</p>
<h3>Stop clustering</h3>
<p>Conditional orders from unleveraged traders sit in roughly the same places as liquidation thresholds from leveraged ones. Both convert into market sells at about the same price. A cluster of stops a few percent below spot effectively adds size to the cascade at the worst possible moment, and each triggered stop is a new market order with no patience and no limit.</p>
<h3>Backstops: insurance funds and auto-deleveraging</h3>
<p>Venues absorb losses that exceed a liquidated position&#8217;s collateral through an insurance fund, and when that is exhausted, through auto-deleveraging, which closes profitable opposing positions at a set price to restore balance. Both mechanisms protect the venue&#8217;s solvency, not your P&#038;L. Auto-deleveraging means a correctly positioned trader can be exited involuntarily during a liquidation cascade, and that exit is a realised disposal for accounting purposes whether or not it was your decision.</p>
<h3>Funding and basis</h3>
<p>After the forced selling stops, perpetual funding and the futures basis reprice. A violent move often leaves funding at an extreme, paying one side and charging the other until positioning normalises. This is the slow part of the cascade: price can recover within minutes while the cost of carry stays distorted for days.</p>
<h2>The stages of a cascade, and what each one looks like</h2>
<p>Most cascades follow the same sequence, though the time between stages varies by venue and by how much leverage was stacked in one place.</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>Stage</th>
<th>What triggers it</th>
<th>What participants observe</th>
</tr>
</thead>
<tbody>
<tr>
<td>Initial break</td>
<td>Ordinary volatility reaches a cluster of thresholds</td>
<td>Small move on rising volume</td>
</tr>
<tr>
<td>Forced market sells</td>
<td>Positions fall below maintenance requirements</td>
<td>Accelerating candles, widening spread</td>
</tr>
<tr>
<td>Stop cascade</td>
<td>Conditional orders fire below the break</td>
<td>Volume spike with little price recovery</td>
</tr>
<tr>
<td>Backstop absorption</td>
<td>Insurance fund or auto-deleveraging engages</td>
<td>Abrupt wick, then a pause</td>
</tr>
<tr>
<td>Carry repricing</td>
<td>Funding and basis reset to the new level</td>
<td>Extreme funding, thin two-way liquidity</td>
</tr>
<tr>
<td>Normalisation</td>
<td>Positioning clears, market makers return</td>
<td>Range forms, spread narrows</td>
</tr>
</tbody>
</table></div>
<p>Read that table as a checklist for the next event rather than a forecast. If stages two and three are underway while the spread is still wide, the loop is live and any new position is being opened into the most expensive liquidity of the month.</p>
<blockquote><p>The uncomfortable arithmetic of a liquidation cascade is that your threshold is set by your leverage, but your fill is set by everyone else&#8217;s. You control the first number and none of the second.</p></blockquote>
<h2>Reducing your exposure before the next liquidation cascade</h2>
<p>You cannot remove cascade risk from a leveraged position, but you can decide in advance how much of it you carry. The routine below takes about twenty minutes per account and is worth repeating after any large move.</p>
<ol>
<li>List every leveraged position with its entry, size, margin mode and liquidation price.</li>
<li>Compute the percentage distance from the current mark to each liquidation price. Anything inside the normal daily range is close to a coin flip.</li>
<li>Check whether those prices sit near round numbers or recent highs and lows, where stops and thresholds tend to concentrate.</li>
<li>Size the position against visible depth within a few percent of the mark, not against headline volume.</li>
<li>Decide what collateral you would add, and at what price, before the move happens rather than during it.</li>
<li>Write down the size you would accept being auto-deleveraged out of, and cut anything above it.</li>
</ol>
<p>As a sanity check, take 10,000 in collateral at 5x, so 50,000 notional. A 15% adverse move costs 7,500, which is 75% of the collateral before any liquidation penalty. At 10x the same move takes the position to zero. The leverage multiple is not the risk setting; the distance to the threshold is.</p>
<p>The post <a href="https://www.ladyww.net/liquidation-cascades/">Liquidation Cascades: How One Position Takes Out Ten</a> appeared first on <a href="https://www.ladyww.net">LadyChain</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.ladyww.net/liquidation-cascades/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>
		<item>
		<title>Funding: The Cost of Holding a Perp</title>
		<link>https://www.ladyww.net/funding-cost-perp/</link>
					<comments>https://www.ladyww.net/funding-cost-perp/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Tue, 27 Oct 2026 08:02:21 +0000</pubDate>
				<category><![CDATA[Markets]]></category>
		<category><![CDATA[Derivatives]]></category>
		<category><![CDATA[Funding Interval]]></category>
		<category><![CDATA[Funding Rate]]></category>
		<category><![CDATA[Holding Cost]]></category>
		<category><![CDATA[Leverage Risk]]></category>
		<category><![CDATA[Market Mechanics]]></category>
		<category><![CDATA[Perp Trading]]></category>
		<category><![CDATA[Perpetual Futures]]></category>
		<category><![CDATA[Position Costing]]></category>
		<category><![CDATA[Risk Management]]></category>
		<guid isPermaLink="false">https://www.ladyww.net/funding-cost-perp/</guid>

					<description><![CDATA[<p>A perpetual future has no expiry, so nothing forces its price to converge on spot. The funding rate is the mechanism that does that job instead: a periodic payment between [&#8230;]</p>
<p>The post <a href="https://www.ladyww.net/funding-cost-perp/">Funding: The Cost of Holding a Perp</a> appeared first on <a href="https://www.ladyww.net">LadyChain</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>A perpetual future has no expiry, so nothing forces its price to converge on spot. The funding rate is the mechanism that does that job instead: a periodic payment between longs and shorts that makes holding the expensive side progressively more costly.</p>
<p>For most traders the funding rate is a line item they notice after the fact. It is quoted as a small percentage, sometimes four decimal places, which makes it look negligible. Multiplied by three payments a day and a leveraged notional, a funding rate is frequently the largest single cost of a position that does not move.</p>
<ul>
<li><strong>Funding is a transfer, not a fee.</strong> One side of the market pays the other. The venue usually keeps none of it, which is why it does not appear in fee schedules.</li>
<li><strong>The rate is periodic, so it compounds against you.</strong> A rate quoted per interval must be multiplied by the number of intervals you hold, not read as a one-off charge.</li>
<li><strong>Notional, not margin, is the base.</strong> Funding is charged on position size, so leverage multiplies the cost relative to the capital you actually posted.</li>
<li><strong>You pay only if you hold at the timestamp.</strong> Positions opened and closed between funding times incur nothing, which makes holding time a decision rather than a detail.</li>
</ul>
<h2>What a funding rate is actually paying for</h2>
<p>It is paying for the difference between the perpetual contract and the spot market. When the perp trades above spot, longs are paying a premium for exposure they could otherwise get by buying the asset, so the rate turns positive and longs pay shorts. When the perp trades below spot, the sign flips.</p>
<p>That is the whole design. The payment is an incentive to take the other side, and its size is set by how far the perp has drifted from the underlying index. A large positive rate is not a signal that the market is right; it is a signal that one side is crowded enough to be charged for it.</p>
<p>Two consequences follow. Funding is a cost of consensus: the more people agree with your position, the more you pay to hold it. And a high rate is self-correcting, because it makes the crowded side expensive enough that some participants close or flip.</p>
<h2>How the funding rate is calculated and paid</h2>
<p>The mechanics vary by venue, but the shape is consistent, and the details are where most cost estimates go wrong.</p>
<h3>The interval is the multiplier</h3>
<p>Rates are quoted per funding interval, and intervals commonly run at eight hours, though some venues use one, four or variable windows. An eight-hour interval means three payments a day. A rate of 0.01 percent per interval is 0.03 percent per day, not 0.01 percent per day.</p>
<p>Reading a rate without checking the interval misstates cost by a factor of three or eight — the most common arithmetic error in position costing.</p>
<h3>Clamps and caps change the picture</h3>
<p>Most venues apply a cap to the funding rate and may combine a premium index with a fixed interest component. In quiet markets the premium is small and the interest component dominates, so a positive rate can persist even when the perp trades near spot.</p>
<p>Caps limit how extreme a rate can get in one interval, but not the total: a capped rate applied for weeks still accumulates.</p>
<h3>Who pays whom, and when</h3>
<p>Payment occurs at fixed timestamps. If you are long and the rate is positive, you pay; if you are short, you receive. Positions opened after the timestamp and closed before the next incur nothing.</p>
<p>This creates a practical asymmetry: a position held for twenty-three hours across two funding times can cost more than one held for twenty-five hours across one. Duration is not the variable that matters — timestamp exposure is.</p>
<blockquote><p>Funding converts a directional bet into a bet on direction plus time. Traders who ignore the second term are often right about the market and still down on the position.</p></blockquote>
<h2>Worked example: the cost of holding one week</h2>
<p>Take a long position with $10,000 of notional exposure at a funding rate of 0.0100 percent per eight-hour interval, three intervals a day.</p>
<p>Cost per interval is 0.0001 × $10,000 = $1.00. Per day that is 3 × $1.00 = $3.00. Over seven days it is $21.00, which is 0.21 percent of notional.</p>
<p>Annualised, the same rate implies 0.0001 × 3 × 365 = 0.1095, or about 10.95 percent per year. That is the number worth comparing against, because a rate that looks like a rounding error per interval is a double-digit annual cost when it persists.</p>
<p>Now change one input. At 0.0300 percent per interval, cost per interval is $3.00, per day $9.00, per week $63.00, and the annualised figure is about 32.85 percent. The position has not moved and the loss is six times larger, entirely from the rate.</p>
<p>Now add leverage. If the $10,000 notional was opened with $1,000 of margin, the weekly funding at 0.0100 percent is $21.00 against $1,000 of capital — 2.1 percent of margin in a week. To break even on funding alone, the underlying has to appreciate 0.21 percent. At the higher rate, the required move is 0.63 percent per week just to stand still.</p>
<p>Finally, compare against trading costs. Assume 0.05 percent per side for illustration, so a round trip on $10,000 costs $5.00 each way, or $10.00. At the lower rate, a week of funding costs $21.00 — more than double the round-trip fee. Over a month, funding dominates: roughly $90 against $10.</p>
<h2>Comparing holding costs across venues</h2>
<p>Because intervals and formulas differ, two venues quoting the same-looking rate can charge different amounts for the same position.</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>What to compare</th>
<th>Why it changes the cost</th>
<th>Where to find it</th>
</tr>
</thead>
<tbody>
<tr>
<td>Funding interval</td>
<td>Three payments a day versus one triples the daily charge</td>
<td>Contract specifications</td>
</tr>
<tr>
<td>Rate cap and floor</td>
<td>Limits how extreme a single interval can be</td>
<td>Funding methodology page</td>
</tr>
<tr>
<td>Index composition</td>
<td>Different spot references produce different premiums</td>
<td>Index definition</td>
</tr>
<tr>
<td>Historical rate distribution</td>
<td>A single snapshot is not a cost estimate</td>
<td>Funding history charts</td>
</tr>
<tr>
<td>Maker and taker fees</td>
<td>Small next to persistent funding, large on short holds</td>
<td>Fee schedule</td>
</tr>
<tr>
<td>Liquidation and margin rules</td>
<td>Determine whether the position survives long enough to matter</td>
<td>Risk documentation</td>
</tr>
</tbody>
</table></div>
<p>The fourth row is the one most often skipped. A rate observed now says little about the average you will pay over a month, because funding responds to positioning and can change sign within days.</p>
<h2>When funding becomes the dominant cost</h2>
<p>Funding dominates when the position is held long enough and the rate is persistent enough that trading fees stop being the main expense. That condition is common in trending markets, where the crowded side pays continuously.</p>
<h3>Short holds versus long holds</h3>
<p>For a position held hours, fees and spread usually outweigh funding, and interval timing can avoid payment entirely. For one held weeks, the ranking inverts.</p>
<h3>The crowded-side problem</h3>
<p>A high positive rate means longs are paying to be long. If your thesis is that the price rises, you are paying for agreement. The position can be correct and still lose money if the move is smaller than the accumulated funding.</p>
<p>The post <a href="https://www.ladyww.net/funding-cost-perp/">Funding: The Cost of Holding a Perp</a> appeared first on <a href="https://www.ladyww.net">LadyChain</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.ladyww.net/funding-cost-perp/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
