Known limits

These limits describe the source and deployment records reviewed on September 10, 2026. The live application may expose a subset according to its network, API version and configuration.

Basket construction and accounting

Limit	Current behavior
Constituents	2–10 distinct token contracts
Launch targets	Every weight is positive; weights total 10,000 basis points, or 100%
Initial funding	Each constituent must satisfy a minimum of 1,000 raw token units
Initial share denomination	One gross share with 18 decimals; this does not peg its value to 1 ETH or $1
Later issuance	Minimum gross amount is 10^12 raw share units, with per-constituent minimums also enforced
Basket changes	Fixed baskets do not add or remove constituents, change issuance-fee terms, or automatically rebalance
Final redemption	Burning the final shares permanently closes further issuance; outstanding claims remain

Raw units depend on token decimals. Passing a minimum in one asset does not imply that the same displayed quantity works for another asset. Small operations can fail their minimums or have material integer rounding.

Only actual token reserves back proportional issuance. Unsolicited token transfers do not become accounted issuance backing or increase a user’s share entitlement.

Token compatibility

Exact transfer amounts are required in the reviewed contracts. Fee-on-transfer, rebasing, restricted or otherwise unusual tokens may be unsupported or become incompatible later. A token contract being discoverable does not certify its behavior, issuer, future availability or investment quality.

The Stock tokens catalog checks the Robinhood registry and active mainnet deployments. Broader token discovery can include markets outside the app’s configured trading venue. A listed token may therefore have no route the application can use.

Trading routes

Native launch and underlying mint/redeem quotes use a configured V3 venue. They prefer a usable direct route and can consider bounded two-hop alternatives. The route search is not a search of every exchange and does not promise global best execution.

Current native quotes expire after two minutes, use 0.5% slippage bounds, and reject execution impact above 5% relative to the fee-adjusted pool spot rate. These are implementation bounds, not a valuation oracle or a promise of returns. The signed transaction’s actual limits govern execution.

All nonzero underlying swap legs need executable routes. Independent basket-leg quotes reject shared pools, so a selection may fail even when each token has a market. Changing trade size can help a size-dependent quote, but it cannot create missing liquidity.

An ETH sale through the underlying route is atomic: the burn, claims and swaps complete together or revert. Independent in-kind redemption and per-token claims provide a separate way to withdraw underlying assets, subject to each token’s ability to pay.

ETF pool liquidity

Area	Current limit
Quote assets	WETH plus one configured additional token; the mainnet record uses USDG
Fee tiers	0.01%, 0.05%, 0.3% and 1%
Pool funding	Separate from basket creation, with any required share approval
Supported position	Full range; position NFT goes to its receiver
Liquidity lock	None provided by this flow; the position owner can withdraw
In-app position tools	No position withdrawal or fee-collection interface in this release
Pool route selection	Bounded candidate search; one path executes, without splitting the order across ETF pools
USDG buys and sells	Use ETF pool swaps; USDG does not directly mint or redeem through the basket in this release

Basket creation can succeed even if later pool funding fails. Resume the liquidity step from the existing basket. A pool address, token balance or third-party listing alone is not evidence of executable liquidity for your amount.

Prices and portfolio information

The app does not provide oracle-backed USD NAV or verified current market-value weights. Launch target charts describe targets; pool prices and executable trade estimates have different meanings. Neither is a guaranteed peg to the backing.

The implementation record also lists no USD NAV/performance charts, no claim history synchronized across all devices, and no general recovery for every replacement-transaction case. Discovery and holdings may depend on indexing coverage and delay. Locally saved receipt and claim information can supplement chain records but should not be treated as a complete portable portfolio history.

Wallets and availability

The documented browser trial uses an injected EVM wallet, such as MetaMask in Chrome. This is not a claim that every wallet, mobile browser or account type has been validated. The implementation record lists ERC-1271 metadata signatures as unsupported.

API, RPC, indexer and external-app availability can affect discovery, quotes and receipt recovery. An old API may leave new controls hidden. Check release status for the distinction between implemented features, recorded activation and current live verification.