FAQ & glossary
Answers to common questions about basket shares, trading, fees and terminology.
Is an ETF share the same as $RRR?
No. Each basket issues its own ERC-20 share token representing proportional claims on that basket’s accounted reserves. $RRR is the planned protocol token and is not deployed in the reviewed release. A basket symbol or a trial token name does not identify $RRR.
Does one basket share equal one dollar or one ETH?
No. The initial gross supply is one 18-decimal share. That is a denomination choice. Its backing depends on the assets and quantities supplied; its pool price depends on the market. There is no promised dollar or ETH peg.
Do my target weights remain fixed?
The declared targets remain part of the basket configuration, but their market values can drift. Native launch weights allocate the initial ETH budget. Received token quantities reflect execution prices and fees. Later minting follows current reserve proportions, and a fixed community basket does not rebalance itself.
What is the difference between minting and a pool swap?
Minting deposits the required constituent proportions and issues new backed shares. A pool swap transfers existing shares between a trader and an ETF pool. Minting changes share supply and backing together; a pool swap does not. The applicable fees and executable prices can differ.
Why can I see a token but not buy it or launch a basket with it?
Discovery and execution use different evidence. A directory entry may exist before there is enough usable liquidity in the configured venue. Quotes also depend on trade size, token behavior, allowed routes and pool conflicts. A visible listing is not a promise that any amount can trade.
Can I exit when there is no ETF pool?
An ETF pool is not required for direct in-kind redemption. You can burn shares into proportional constituent claims and claim each token independently. Selling the result into ETH additionally requires usable underlying-token markets. Token restrictions or deficits can still prevent payment of an affected constituent.
What if one constituent stops transferring?
The fixed-vault implementation creates redemption claims without calling the constituent tokens and pays each token separately. Healthy claims can remain payable independently. The affected claim still depends on its token contract and sufficient token-local coverage; the system cannot recover an asset its issuer has frozen or removed.
Can a creator change my basket or withdraw its backing?
The reviewed fixed-basket vault has no owner, upgrade, asset-sweep or portfolio-trading entry point. Its constituents and issuance-fee terms are set at creation. A creator’s own shares have the same proportional exit mechanism as other shares. Constituent issuers can still have powers in their separate token contracts.
Is liquidity locked?
No. The supported pool-funding flow issues a position NFT to the selected receiver. That owner can withdraw liquidity through the position manager. Other providers’ positions remain their own. A successful basket launch does not guarantee permanent pool liquidity.
Which fee model applies today?
The reviewed fixed vault charges an immutable 0–1% issuance fee selected when the basket is created. The fee applies to newly issued shares, including the seed. Pool swaps have pool trading fees, and all transactions can require gas. The planned creation, redemption and annual fees on the $RRR page are a separate, unimplemented proposal; see $RRR economics.
Does disconnecting remove token approvals?
No. Disconnecting clears the app’s connected account and may revoke the site’s account permission in supported wallets. An on-chain token allowance remains until it is spent or changed through a transaction.
Has the protocol been audited?
The reviewed repository reports no independent contract audit. It records automated tests, local fork checks and deployment bytecode validation. Public explorer source verification is pending in that record. See security and trust for what each form of evidence establishes.
Glossary
| Term | Meaning in these docs |
|---|---|
| Basket / ETF | The app’s token basket and its share token; this name alone does not establish regulatory status or issuer rights |
| Constituent | A token held as part of a basket’s backing |
| Share | The basket’s ERC-20 token, used to measure proportional ownership of active reserves |
| Active reserve | Accounted constituent backing belonging to current shares, excluding pending withdrawal claims |
| Mint / issuance | Deposit backing and create new shares |
| Gross shares | All new shares issued before separating the issuance fee |
| Net shares | Shares sent to the receiver after the issuance fee |
| Redemption | Burn shares and reserve the corresponding constituent amounts for withdrawal |
| Claim | Payment of one reserved constituent amount to the receiver fixed at redemption |
| In kind | Supplying or receiving the constituent tokens themselves |
| Pool swap | Exchange existing shares or tokens through a liquidity pool |
| WETH | Wrapped ETH used by token-based pools and routers |
| Settlement token | Asset used to pay for a trade or receive its proceeds |
| Slippage bound | A signed limit on acceptable execution amounts |
| Price impact | Change in execution price associated with the requested trade size |
| Basis point / bps | One hundredth of a percentage point; 100 bps equals 1% |
| NAV | Net asset value; these docs do not claim the app has an oracle-backed USD NAV |
| Vault | Contract that holds basket constituents and manages share/claim accounting |
| Factory / registry | Contract that creates baskets and records their membership |
| Position NFT | Ownership record for a V3 liquidity position |
| Fork test | A test on a local copy of chain state, without sending that test’s trades to the public chain |
For exact identities, use networks and addresses. For implemented boundaries, use known limits.