Developer reference
Scope and scale
Our 1,000-holding target, the fund’s registry-free design, and practical withdrawal limits.
Loading…
Browse documentation
Developer reference
Our 1,000-holding target, the fund’s registry-free design, and practical withdrawal limits.
Loading…
Developer reference
Our 1,000-holding target, the fund’s registry-free design, and practical withdrawal limits.
GlazeCorp’s product scope is decentralized funds with up to 1,000 assets per fund on Robinhood Chain. This is a product scale target, not a fixed contract maximum or an end-to-end performance guarantee.
The goal is a complete fund experience for broad funds: launching a fund, discovering its holdings, allocating capital and withdrawing underlying assets. The number of holdings is one measure of that ambition; usability at that size matters just as much.
The treasury has no asset registry and no hard-coded asset-count limit. ERC-20 balances live in the individual token contracts, at the treasury’s address. Adding another holding does not require the treasury to maintain or iterate over a master list.
That architecture can accommodate broad funds, but an address holding many tokens is only one part of a usable fund. The interface and indexer must also discover the holdings, read balances reliably and distinguish missing prices from zero value.
Strategies exchange mining revenue for their payment tokens. Allocation directs the split of future revenue between active strategies; it does not directly set the weights of existing holdings.
One thousand asset balances do not imply one thousand active strategies, automatic rebalancing or reliable tracking of an external index. Those are separate questions that need their own operational and performance evidence.
A withdrawal processes the token addresses selected by the holder. There is no fixed list-length cap in the treasury, but each balance read and transfer consumes gas. Practical transaction size depends on the network and the behavior of every selected token. A large fund may not fit in one transaction.
Selection changes the payout. Burning Coin for some assets permanently forfeits the omitted assets’ share for those burned coins. Splitting the list across successive burns is not equivalent to withdrawing the full set of assets. Always review the selected holdings and the forfeiture warning before confirming.
Unsupported or failing token behavior can also prevent a selected withdrawal from completing. See Withdrawal mechanics and Risks.
The source establishes that there is no fixed asset-count cap. It does not establish that every 1,000-asset fund can be discovered, priced, displayed and withdrawn under production network conditions.
End-to-end validation needs representative token fixtures, reliable discovery, large-list interface checks, measured transaction gas and clear handling of unavailable or incompatible assets. The asset count alone does not prove that every supported action works at that scale.