This proposal would change the token that non-Quote assets are swapped to on Osmosis from USDC to Alloyed BTC.
Background
Osmosis currently sends 55% of non-OSMO tokens collected via Taker fees to the community pool.
These are sent directly if they are an existing Quote asset and swapped to a denom set by governance if not.
This denom is currently set to USDC via Noble. This proposal asks that it be adjusted to alloyed BTC to increase the community pool’s regular accumulation of BTC. This should reduce the requirement for rebalancing proposals such as Proposal 948.
Setting to be changed
Subspace: poolmanager
Parameter:
CommunityPoolDenomToSwapNonWhitelistedAssetsTo
Current setting: ibc/498A0751C798A0D9A389AA3691123DADA57DAA4FE165D5C75894505B876BA6E4
New Setting:
factory/osmo1z6r6qdknhgsc0zeracktgpcxf43j6sekq07nw8sxduc9lg0qjjlqfu25e3/alloyed/allBTC
Target on-chain Date: 1st July 2025
1 Like
What is the current average daily acquisition of USDC?
To give an idea of how much potential we are talking about.
I also am a bit hesitant to the exact purpose of the community pool and whether we should want a larger volatile part of it, or have it in stables. Ofcourse it misses out on potential value increases, but it wins against potential value declines…
I should clarify here, this currently is hardly any revenue at all since the collector whitelist is the quote asset whitelist - which is pretty much all assets in use on Osmosis because of the pending permissionless implementation.
After the next upgrade this will be separated and we should narrow the collector assets down to a few, which will cause this default denom to be used far more - probably 1k or so a day based on current levels.
Right now we collect a high percentage of USDC (50% of non OSMO taker fees) without the default denom supplementing this much, so after this change we would collect even more stable coins compared to volatiles.
To put things in perspective, when is this upgrade expected?
Because it would make a difference for me, since it changes the playing field when the change is applied.
Probably in around a month/two.
A lot of recent chaindev work recently has ended up as either a patch release, contract work, or more resolving tech debt/patching with no fixed release required yet.