Start here
Welcome to GlazeCorp
Learn how funds work, use a fund, or launch one of your own.
Loading…
Browse documentation
Start here
Learn how funds work, use a fund, or launch one of your own.
Loading…
Start here
Learn how funds work, use a fund, or launch one of your own.
A GlazeCorp fund holds a basket of tokens. Buy its fund token for a share of the assets it holds. GlazeCorp lets you trade that token or burn it to withdraw a share of those assets. The docs explain what you hold, how the treasury acquires assets, and which decisions remain with the creator.
You do not need to mine, allocate or fill auctions to hold a fund token.
A fund token is your proportional claim on the treasury's listed assets. The fund holds its assets in an onchain treasury. The token's market price can differ from the value of its holdings.
Start by exploring funds. Check the contract address, actual holdings, trading liquidity and who allocates capital.
| I want to… | Read |
|---|---|
| Buy or sell a fund token | Buy and sell |
| Exchange tokens for treasury assets | Withdraw assets |
| Earn newly issued tokens | Use the Mine |
| Allocate capital and claim available rewards | Allocate and claim rewards |
| Sell an asset to a fund for USDG | Fill an auction |
Selling and withdrawing are different exits. Selling uses market liquidity. Withdrawing burns your tokens for a proportional share of the listed assets; your share of anything left off the list is permanently forfeited for that burn.
Launch a fund token explains the Launch page, seed liquidity, fees and allocation choices. After launch, you can add asset strategies and manage the settings exposed by the FundController.
A community-led fund lets holders allocate capital. A manager-led fund gives that role to one or more approved manager wallets. Neither mode automatically sells or rebalances existing holdings. Read creator authority before choosing or joining a fund: the creator can also change fees and the destination of future mining revenue.
Start with the contract architecture, configured addresses, and SDK and subgraph. Protocol mechanics explain accounting and transaction bounds; Contract API contains the generated function reference.
Check the deployed contract version before constructing a transaction. The audit, source reference and live deployment are separate things.