<?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>Commission Archives - LadyChain</title>
	<atom:link href="https://www.ladyww.net/tag/commission/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.ladyww.net/tag/commission/</link>
	<description>Crypto fees, wallets and offers — checked against the terms page</description>
	<lastBuildDate>Tue, 27 Oct 2026 14:02:50 +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>Commission Archives - LadyChain</title>
	<link>https://www.ladyww.net/tag/commission/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Staking Pools: What You Give Up</title>
		<link>https://www.ladyww.net/staking-pools/</link>
					<comments>https://www.ladyww.net/staking-pools/#respond</comments>
		
		<dc:creator><![CDATA[]]></dc:creator>
		<pubDate>Tue, 27 Oct 2026 14:02:50 +0000</pubDate>
				<category><![CDATA[Staking]]></category>
		<category><![CDATA[Commission]]></category>
		<category><![CDATA[Custody Risk]]></category>
		<category><![CDATA[Delegation]]></category>
		<category><![CDATA[Liquid Staking]]></category>
		<category><![CDATA[Pooled Staking]]></category>
		<category><![CDATA[Slashing]]></category>
		<category><![CDATA[Staking Pools]]></category>
		<category><![CDATA[Unbonding]]></category>
		<category><![CDATA[Validator Risk]]></category>
		<category><![CDATA[Yield Mechanics]]></category>
		<guid isPermaLink="false">https://www.ladyww.net/staking-pools/</guid>

					<description><![CDATA[<p>A staking pool is a contract that accepts your tokens, stakes them under someone else&#8217;s operational control, and returns a transferable claim on the balance. You keep economic exposure; you [&#8230;]</p>
<p>The post <a href="https://www.ladyww.net/staking-pools/">Staking Pools: What You Give Up</a> appeared first on <a href="https://www.ladyww.net">LadyChain</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>A staking pool is a contract that accepts your tokens, stakes them under someone else&#8217;s operational control, and returns a transferable claim on the balance. You keep economic exposure; you hand over the keys that make the exposure real.</p>
<p>The trade is usually framed as commission versus convenience. That framing hides most of the cost. A staking pool changes who can be slashed, who decides when you exit, what you actually hold while you are in it, and what happens if the operator stops answering.</p>
<ul>
<li><strong>You hold a claim, not the staked asset.</strong> The pool&#8217;s share token is only as good as the contract and the operator behind it.</li>
<li><strong>Commission is the visible cost.</strong> Socialised penalties, exit queues and governance loss are the ones that rarely appear in a comparison table.</li>
<li><strong>Pooled staking is not risk-free staking.</strong> Penalties are shared across participants, including ones caused by the operator.</li>
<li><strong>Exit terms matter more than entry terms.</strong> Read the unbonding and redemption rules before depositing, not after.</li>
</ul>
<h2>What a staking pool actually holds</h2>
<p>The contract holds two things: the staked assets under the operator&#8217;s validator set, and a ledger of who owns what. The first is on-chain and auditable. The second is where the differences between products live.</p>
<h3>Custody and control</h3>
<p>In a non-custodial pool, the deposit contract holds the assets and the operator controls withdrawal keys or validator operations. You can usually see the balance but not move it. In a custodial arrangement, an intermediary holds both, and your claim is against that intermediary rather than against the chain.</p>
<p>The distinction matters at the worst moment. If the operator&#8217;s infrastructure fails, non-custodial pools typically still let you exit through the contract after the unbonding period. Custodial arrangements depend on the intermediary&#8217;s solvency and terms of service, which is a different kind of risk entirely.</p>
<h3>How the share accounting works</h3>
<p>Most pools issue a receipt token whose value tracks the pool&#8217;s assets per share. Deposits mint shares at the current ratio; rewards increase the assets behind each share rather than the number of shares you hold. Withdrawals burn shares at the ratio in force at that moment.</p>
<p>Two consequences follow. First, your balance in the receipt token does not grow even though your claim does, which confuses people tracking rewards by token count. Second, the ratio can fall as well as rise — a slashing event reduces assets per share for everyone, without changing anyone&#8217;s share count.</p>
<h2>The costs that are not the commission</h2>
<p>Commission is a stated percentage of rewards, typically taken before distribution. The rest of the cost is structural, and it shows up as a smaller balance or a longer exit rather than a line item.</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>Cost</th>
<th>How it appears</th>
<th>Who bears it</th>
<th>Typical shape</th>
</tr>
</thead>
<tbody>
<tr>
<td>Operator commission</td>
<td>Deducted from rewards before payout</td>
<td>All depositors equally</td>
<td>Stated up front, varies widely by venue</td>
</tr>
<tr>
<td>Socialised penalties</td>
<td>Assets per share fall after a slashing event</td>
<td>All depositors, including careful ones</td>
<td>Rare, but not bounded by your own behaviour</td>
</tr>
<tr>
<td>Exit queue</td>
<td>Redemption delayed by unbonding rules</td>
<td>Anyone leaving during congestion</td>
<td>Fixed by protocol, occasionally longer in practice</td>
</tr>
<tr>
<td>Receipt-token risk</td>
<td>Claim trades at a discount or loses a market</td>
<td>Anyone needing liquidity before unbonding</td>
<td>Depends on the venue&#8217;s depth</td>
</tr>
<tr>
<td>Governance and voting</td>
<td>Voting power moves to the operator</td>
<td>Depositors who care about protocol decisions</td>
<td>Permanent for the duration of the deposit</td>
</tr>
</tbody>
</table></div>
<blockquote><p>A pool&#8217;s receipt token is a promise about someone else&#8217;s operational competence. Price it as a claim on an operator, not as the underlying asset with a yield attached.</p></blockquote>
<h3>Commission, worked through</h3>
<p>A hypothetical pool holds 1,000 units against 1,000 receipt tokens, so one token equals one unit. You deposit 100 units and receive 100 tokens; the pool now holds 1,100 units against 1,100 tokens.</p>
<p>Over a year the pool earns 88 units gross — 8% on 1,100. The operator takes a 10% commission, or 8.8 units, leaving 79.2 units added to the pool. Assets per token become 1,179.2 ÷ 1,100 = 1.0720. Your 100 tokens redeem for 107.20 units, a 7.20% return.</p>
<p>Staking the same 100 units directly at the same gross rate would have produced 8.00 units. The gap is 0.80 units per year. Whether that is cheap depends on what running the infrastructure would have cost you — and on whether the pool&#8217;s 8% gross assumption holds after downtime, which it often does not.</p>
<h2>Failure modes you inherit from the operator</h2>
<p>Joining a pool means inheriting the operator&#8217;s operational record. You do not get to audit it in advance, and you cannot intervene once you are in.</p>
<h3>Slashing and penalty socialisation</h3>
<p>Slashing rules are set by the protocol, not the pool. In most designs a penalty is applied to the stake that caused it, which for a pool means everyone&#8217;s assets per share drop. The depositor who joined yesterday absorbs part of a mistake made before they arrived, and the depositor who leaves tomorrow does not.</p>
<p>Some operators maintain an insurance buffer or absorb penalties from their own stake. That is a commercial commitment, not a protocol guarantee, and it is worth reading exactly how it is funded and capped.</p>
<h3>Downtime, commission changes and governance</h3>
<p>Validators go offline. Missed duties usually produce small, continuous penalties rather than a dramatic event, and the depositor sees them as a slightly slower-growing balance. Commission terms can often be changed within limits the contract allows, and those limits are worth locating before deposit rather than after a change.</p>
<p>Governance rights are the quietest loss. In networks where staked tokens vote, delegating to a pool usually transfers that vote to the operator&#8217;s stated policy. If you would have voted differently on a parameter change, that preference disappears.</p>
<h2>When a staking pool is the wrong tool</h2>
<p>It is the wrong tool when your reason for staking is anything other than yield on a balance you will not need quickly.</p>
<p>If you need liquidity inside the unbonding window, either accept the receipt token&#8217;s market price or do not stake. If you hold a position large enough that your own validator is economical, the commission saving may exceed the operational cost — though that calculation depends on hardware, monitoring and your tolerance for being on call.</p>
<p>If the tokens carry governance weight you intend to use, pooled staking removes it. And if you cannot explain in one sentence how the pool&#8217;s receipt token is redeemed, you are relying on an assumption rather than a mechanism.</p>
<p>The post <a href="https://www.ladyww.net/staking-pools/">Staking Pools: What You Give Up</a> appeared first on <a href="https://www.ladyww.net">LadyChain</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.ladyww.net/staking-pools/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
