{"id":227774,"date":"2026-09-15T12:01:33","date_gmt":"2026-09-15T12:01:33","guid":{"rendered":"https:\/\/mycryptomania.com\/?p=227774"},"modified":"2026-09-15T12:01:33","modified_gmt":"2026-09-15T12:01:33","slug":"a-token-burn-cuts-supply-whose-share-gets-bigger","status":"publish","type":"post","link":"https:\/\/mycryptomania.com\/?p=227774","title":{"rendered":"A Token Burn Cuts Supply. Whose Share Gets Bigger?"},"content":{"rendered":"

The same supply cut can leave very different allocations behind. Three worked examples show\u00a0why.<\/em><\/p>\n

AI-generated editorial illustration of token allocations with pieces\u00a0removed.<\/p>\n

Suppose public holders own 40 of a token\u2019s 100 units. After a 20-token burn, they could still hold 40 tokens and own 50% of the remaining supply. But that identical 50% can describe two very different outcomes for the team and the community reserve.<\/p>\n

AI was used for research and to generate the draft of this article. Mobina Ebrahimi works with Forvest in research and\u00a0SEO.<\/em><\/p>\n

The missing detail is the source of the burned tokens. Follow each allocation through the reduction, and the difference becomes\u00a0visible.<\/p>\n

One burn size, three allocations<\/h3>\n

Start with an entirely hypothetical allocation: 20 tokens held by the team, 40 by public holders, and 40 in a community reserve. The groups do not overlap. Each scenario removes 20 tokens, leaving 80. No other issuance or transfers occur.<\/p>\n

These are accounting examples, not CLOUD allocations or proposals by a real project. They do not imply that a protocol can take tokens from holders without the required authority or\u00a0consent.<\/p>\n

Original hypothetical calculations. Bar lengths show token counts; percentage labels use the supply remaining in each row. The chart was rendered programmatically with AI assistance.<\/p>\n

Compare the first two burn scenarios: public holders have 40 tokens and a 50% share in both. Yet the team and reserve balances are different.<\/strong><\/p>\n

If the community reserve supplies the burn<\/strong>, the team keeps 20 tokens, public holders keep 40, and the reserve falls to 20. Their shares become 25%, 50% and\u00a025%.<\/p>\n

If the team supplies the burn<\/strong>, its allocation falls to zero. Public holders and the reserve each keep 40 tokens, giving each a 50% share. The headline percentage for public holders has concealed which other allocation disappeared.<\/p>\n

If every group contributes proportionally<\/strong>, each loses 20% of its balance. The team keeps 16 tokens, public holders 32, and the reserve 32. Their shares stay at 20%, 40% and 40%. For this scenario, assume the same proportional reduction applies within each group to every individual holder.<\/p>\n

All three scenarios remove the same fraction of supply. Only the last leaves every group\u2019s percentage unchanged.<\/p>\n

Calculate balances before percentages<\/h3>\n

For each group, subtract its contribution to the burn before calculating its new\u00a0share:<\/p>\n

Remaining group balance = starting balance \u2212 that group\u2019s burned\u00a0tokens.<\/strong><\/p>\n

New supply share = remaining group balance \u00f7 remaining total supply \u00d7\u00a0100.<\/strong><\/p>\n

Keep both results. In the reserve-only example, public holders move from 40% to 50%: an increase of ten percentage points, or 25% relative to their starting share. Their token count remains\u00a040.<\/p>\n

The team-to-public balance ratio also remains 20:40. Both unchanged groups receive the same percentage multiplier. This example therefore cannot support a claim that the team became more dominant relative to those existing public\u00a0holders.<\/p>\n

This separation between measurement and interpretation is also central to Forvest\u2019s crypto analytics framework<\/a>. Before comparing percentages, establish what each one is measured\u00a0against.<\/p>\n

What a real reserve-burn proposal tells\u00a0us<\/h3>\n

Sanctum\u2019s September 2, 2026 CLOUD proposal<\/a> specifies removing approximately 259 million tokens from the Community Reserve, taking total supply from one billion to about 741 million. The Strategic Reserve would remain. This calculation uses the proposed design; it does not establish approval or execution. Sources were reviewed on September 15.<\/p>\n

The proposal supports a simple accounting split:<\/p>\n

Community Reserve: approximately 259 million to\u00a0zero<\/strong>.All other tokens combined: approximately 741 million before and\u00a0after<\/strong>.<\/p>\n

The second group would represent all remaining supply. This calculation does not establish how the remaining tokens are currently split between the team, investors, and other\u00a0holders.<\/p>\n

A reserve is also a set of future\u00a0choices<\/h3>\n

The allocation check reveals two effects: a percentage changes, and a specific pool has fewer tokens available for later\u00a0use.<\/p>\n

An existing public holder can gain supply share while a reserve loses the inventory that might otherwise support future allocations. Whether keeping that inventory would be worthwhile depends on its permitted uses, who controls it, and the alternatives available.<\/p>\n

A similar disagreement appears in Reserve\u2019s August 2026 unlocking discussion<\/a>. Participants debate permanent supply reduction against retaining tokens for later ecosystem spending. Their disagreement establishes a question worth examining; it does not settle which policy creates more\u00a0value.<\/p>\n

\u201cCommunity reserve\u201d should therefore prompt a document check: who can authorize its use, what it can fund, and which restrictions apply. Those questions belong inside broader project due diligence<\/a>, alongside the allocation figures.<\/p>\n

Apply this to the next announcement<\/h3>\n

If you follow crypto news through source-linked summaries such as Forvest\u2019s News Review<\/a>, open the original announcement before completing the check below. A summary can lead you to the claim; the proposal and execution records provide the evidence for its\u00a0status.<\/p>\n

Record five\u00a0items:<\/p>\n

Event state:<\/strong> the dated proposal, decision or execution evidence. A proposal\u2019s arithmetic does not prove implementation.Supply basis:<\/strong> exactly what the denominator includes. A total-supply calculation is not automatically a circulating-supply calculation.Source allocation:<\/strong> which balances contribute the burned tokens, including any allocation whose contribution is\u00a0zero.Balances and shares:<\/strong> the before-and-after token counts, followed by percentages calculated on the same\u00a0basis.Rights and remaining uses:<\/strong> documented voting or distribution rules, and what the surviving reserves can still\u00a0fund.<\/p>\n

If the project simultaneously issues or transfers tokens, include those changes before interpreting the result. If an input is missing, mark the affected row unresolved. Do not fill a current allocation table with historical balances simply because they are easier to\u00a0find.<\/p>\n

Supply share by itself establishes neither a price gain nor a particular voting or revenue entitlement. Those conclusions need their own evidence.<\/p>\n

In our hypothetical example, burning from the community reserve or the team allocation leaves public holders with the same 40 tokens and the same 50% share. Yet the remaining allocations are very different: one burn leaves a smaller community reserve; the other eliminates the team allocation.<\/p>\n

A holder whose balance stays unchanged gains a larger share when supply shrinks. That answers whose percentage grows. To understand the rest of the change, check whose tokens were removed and what each group still holds. The next time a burn is announced, put those remaining balances beside the headline\u00a0number.<\/p>\n

A Token Burn Cuts Supply. Whose Share Gets Bigger?<\/a> was originally published in Coinmonks<\/a> on Medium, where people are continuing the conversation by highlighting and responding to this story.<\/p>","protected":false},"excerpt":{"rendered":"

The same supply cut can leave very different allocations behind. Three worked examples show\u00a0why. AI-generated editorial illustration of token allocations with pieces\u00a0removed. Suppose public holders own 40 of a token\u2019s 100 units. After a 20-token burn, they could still hold 40 tokens and own 50% of the remaining supply. But that identical 50% can describe […]<\/p>\n","protected":false},"author":0,"featured_media":227775,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-227774","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-interesting"],"_links":{"self":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts\/227774"}],"collection":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=227774"}],"version-history":[{"count":0,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts\/227774\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/media\/227775"}],"wp:attachment":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=227774"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=227774"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=227774"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}