Skip to main content

​
The model and the holdings

A strategy describes the assets a manager chooses and their target weights. A user portfolio is the set of assets held in that user’s smart account. A subscription connects the user portfolio to the manager’s strategy. Many users can follow the same model. Their account balances and positions remain separate. They do not receive a token representing a claim on a pooled MyStacks fund.

​
Target allocations

Target weights express how the manager wants a portfolio to be distributed. For example, a strategy might allocate 50% to Asset A, 30% to Asset B, and 20% to Asset C. These names and weights are illustrative. They are not a supported asset list or an investment recommendation. Prices and portfolio activity can move actual weights away from the target. A rebalance trades assets to move the portfolio toward the intended allocation.

​
Rebalance decisions

Managers save target weights and a recurring schedule through the Manager API. Saving an allocation change does not start an immediate rebalance. The planned execution workflow uses it at the next applicable schedule boundary. The schedule contract defines the accepted UTC presets. Automated scheduled trading is still being built. Each subscriber needs execution based on their own holdings. A shared strategy does not mean every account can execute an identical trade amount. See execution and rebalancing for the transaction flow.

​
Asset coverage

MyStacks is focused on portfolios for tokenised finance. The supported assets depend on the selected networks and available swap routes. The Manager API accepts the supported trading assets on Robinhood Chain. Fee schedules and portfolio analytics also need dedicated documentation as those product details settle.