1
A manager defines a portfolio
The manager chooses assets and assigns target weights. This model is the
strategy that users subscribe to.
2
A user subscribes
The user enrols through the frontend. A user-owned smart account holds the
user’s portfolio assets. The user remains the account owner.
3
The user funds the account and enables automation
The user adds assets and grants delegated permissions for portfolio swaps.
This enables MyStacks to carry out authorised swaps without requesting a
signature for every trade. The funding flow and provider choices are still
being defined.
4
MyStacks coordinates rebalancing
The intended workflow uses the manager’s saved allocation at each applicable
schedule boundary. The backend prepares swaps for each account and submits
them through the execution layer. Automated scheduled trading is still being
built.
5
The user stays in control
The user can revoke the automation permission. Withdrawing assets is a
separate action authorised by the account owner. The manager does not
receive withdrawal authority.
Who does what?
See portfolios and strategies for the investment model.
See smart accounts for the ownership boundary.