Market volume
$FSTR trades on Flap and produces the configured tax.
$FSTR is the strategy layer on top of Flap’s Stocks Vault. Trading tax enters a disclosed vault mandate, buys listed stock tokens or basket shares, and routes the resulting assets to holders.
The value flow remains mechanical. Strategy names and weights define what the vault may buy; chat does not rewrite the mandate.
$FSTR trades on Flap and produces the configured tax.
The disclosed tax route sends assets into the documented Stocks Vault.
The vault acquires stock token S or its published IndexBasketToken.
Stock assets or basket shares accrue against eligible $FSTR holdings.
Auto-pay above the threshold, or holder claim through the tax interface.
The keeper resolves the actual vault type before it interprets the dividend asset.
A single-token RWA vault. The target asset is returned by rwaAsset() and may begin as address(0) until the first tax flow initializes it.
shape: single name
output: one stock token
factory: allowlist requiredThe later single-name vault path. The strategy still resolves one disclosed stock token rather than a discretionary basket.
shape: single name
output: one stock token
policy: fixed at createA basket of one to N supported assets. Holder dividends are represented by the vault’s IndexBasketToken.
shape: basket
output: IB shares
read: supportedAssets()Explore compatible shapes below. This interface demonstrates the schema; it does not change any deployed vault.
Select a mandate to inspect its vault shape, output, and supported allocation.
The keeper may service the mandate. It does not get to invent a different one.
Read FlapTaxVaultTokenCreated from VaultPortal.
Require vaultFactory on the Stocks allowlist.
Read rwaAsset(), basketToken(), and supportedAssets().
Continue only when $FSTR is the documented tax token.
Distribute only when the configured minimum is satisfied.
Halt on unknown factory, depeg, or daily cap.
The strategy name, supported assets, weights, vault factory, tax route, and optional buyback split belong in the deployment schema—not in a changing social post.