Vault Policies
Vault policies define rules that apply to the entire vault. These policies are always enforced regardless of user role or permissions.
Examples: asset allowlists, borrowable assets, timelock.
Examples: asset allowlists, borrowable assets, timelock.
Tokenization Policies
Tokenization policies govern tokenized vault shares and investor interactions. They control subscription, redemption, and fulfillment rules.
Examples: maximum capacity, minimum subscription size, lockup periods, investor allowlists.
Examples: maximum capacity, minimum subscription size, lockup periods, investor allowlists.
Integration Policies
Integration policies define rules specific to individual DeFi protocol connections. Each enabled integration can have its own policy constraints.
Examples: market allowlists, slippage limits.
Examples: market allowlists, slippage limits.
Vault Policies
Asset Allowlist
Asset allowlist defines which tokens a vault can interact with. It is also used as source of truth for pricing vault tokens.Borrowable Assets
This list defines which assets the vault can borrow from DeFi protocols. Tokens held by the vault but not among the asset allowlist or borrowable assets are not included in the vault’s AUM.Transfer Allowlist
By default, delegates can deploy vault capital into DeFi protocols and withdraw it back into the vault, but they cannot transfer assets to arbitrary addresses or personal wallets. The Transfer Allowlist enables vault owners to define approved destinations for vault assets, such as other vaults under the same control. This adds flexibility for internal capital management while preventing unauthorized or unintended transfers.Tokenization Policies
Maximum Capacity
Defines the maximum total value the vault can accept.Minimum Subscription
Defines the minimum amount required for a subscription.Minimum Redemption
Defines the minimum number of shares required for a redemption.Permissioned Fulfillment
By default, only managers can fulfill subscription and redemption requests. If permissionless fulfillment is enabled, anyone, including users and bots, can fulfill eligible requests once they become executable.Investor Allowlists
GLAM Mints support allowlists to further restrict who can subscribe or redeem beyond the default account state. Only pre-approved wallet addresses can receive or interact with minted tokens. This enables jurisdictional compliance, institutional onboarding, and controlled distribution.Investor Blocklists
Blocklists act as an additional enforcement layer by denying specific addresses the ability to receive, hold, or transfer mint tokens. Used to manage sanctions, compromised wallets, or internal policies, blocklisted actions are automatically rejected by the token program.Lockup Periods
Lockup periods impose time-based restrictions on both redemptions and transfers of minted tokens. When enabled, every recipient is subject to a lockup window starting from the moment of mint or token receipt. During this period, transfers and burns (used for redemptions) are blocked at the protocol level. These constraints are enforced via Transfer Hook metadata and GLAM’s Policies program, offering strong, onchain guarantees against premature liquidity events. Lockups help align redemptions with fund terms, prevent early exits, and protect portfolio stability.Integration Policies
Market Allowlists
Market allowlists define which specific markets a vault can access within each supported DeFi protocol. The overall market access for a vault is the combination of all integration-specific market allowlists. For example:- For the Drift Protocol, vault owner can allow only selected spot or perpetual markets.
- For the Kamino Lending, vault owner can specify a list of selected lending pools.
- The Jupiter Swap Allowlist controls which tokens can be swapped into using Jupiter.