Developer reference
Comparing fund designs
How GlazeCorp differs in allocation, backing and withdrawals, with primary-source comparisons.
Loading…
Browse documentation
Developer reference
How GlazeCorp differs in allocation, backing and withdrawals, with primary-source comparisons.
Loading…
Developer reference
How GlazeCorp differs in allocation, backing and withdrawals, with primary-source comparisons.
GlazeCorp lets anyone launch a fund whose treasury purchases can be directed by its holders. Its design combines mining-funded asset accumulation, changing purchase strategies and a treasury that holders can withdraw from. It does not automatically rebalance existing holdings to track target weights.
This comparison covers documented protocol capabilities, not every deployed fund or current interface. Sources were reviewed on September 5, 2026. Asset count, permissions and transaction limits depend on the implementation and network.
| Question | GlazeCorp | Reserve Index DTFs | Index Coop / Index Protocol |
|---|---|---|---|
| How broad can the basket be? | No fixed treasury holding-count cap. A 1,000-holding experience is a target requiring validation. | Documentation describes handfuls to hundreds of tokens. | The cited documentation does not establish a universal asset-count maximum. A product's holding count is not a protocol limit. |
| Can its direction change? | The creator can add strategies or stop future funding of a strategy. Existing holdings remain. | Governance can change assets and target weights. | Managers and enabled modules can modify positions and rebalance. |
| Who allocates capital? | Holders allocate fund tokens in community-led funds; approved manager wallets allocate in manager-led funds. The creator controls eligible strategies. | Configurable token-based governance controls basket decisions. | Product-specific managers, permissions and methodologies. |
| Does it rebalance existing holdings? | No. Allocation weights divide future revenue, not current treasury balances. | Yes, through asset-exchange auctions toward target weights. | Rebalancing modules support changes to basket positions. |
| Can holders withdraw assets? | Burn fund tokens for listed underlying assets. Omitted assets' shares are forfeited for the tokens burned. | Permissionless underlying-asset redemption and NAV-based issuance. | Permissionless underlying-asset redemption; the issuance module depends on the product. |
Reserve capabilities above come from its Index DTF overview. Index Coop capabilities come from its Index Protocol documentation and programmatic redemption guide. These sources describe designs; they are not independent measurements of production performance.
Holders allocate capital. In community mode, committing fund tokens to an eligible strategy increases its share of future mining revenue. This is ongoing allocation, rather than a promise that an allocation immediately changes treasury holdings. Token-holder governance exists elsewhere; the specific allocation-to-revenue mechanism is the useful distinction.
The purchase plan can evolve. The creator can add a route for another asset or permanently stop an existing strategy. Stopping it blocks new allocations and future revenue. Previously accrued revenue and auction balances can still settle into that asset afterward. Existing holdings stay in the treasury and remain redeemable. The final live strategy cannot be stopped. See Managing strategies.
Mining can build backing. After the outgoing miner's share and fees, takeover revenue flows toward strategies that acquire assets for the treasury, after configured allocation rewards. The design connects demand for mining to asset accumulation. It is not a direct conversion of token market capitalization into treasury value. See Price and backing.
Withdrawal is part of the treasury. The treasury has no administrator who can take out its assets or pause its withdrawal (redeem) function. A holder burns fund tokens to receive proportional amounts of listed tokens, subject to token compatibility, rounding and gas. A withdrawal does not promise a cash amount or restore a share of omitted assets.
GlazeCorp's lack of rebalancing means purchase allocations and actual holding weights can diverge. Asset prices move independently, and stopping a strategy does not remove exposure to its existing holdings. Mining adds supply; asset accumulation must be assessed per token as well as in total. A broad fund also makes discovery, pricing and complete withdrawal harder. See Scope and scale.
The reviewed evidence does not support saying that other onchain index protocols generally cap baskets below ten assets, cannot change after deployment, lack holder governance or lack redemption. Nor does it support treating all index protocols as tokens that buy assets only with swap fees. Compare a named protocol and version when making those claims.