Skip to main content
The initial execution model uses direct swaps from each user’s smart account. MyStacks coordinates the transaction for that account. The assets and swap proceeds remain associated with the user portfolio.

​
From a portfolio decision to a trade

1

Prepare the rebalance

The intended workflow uses the manager’s saved allocation at the next applicable schedule boundary. MyStacks determines the trades needed for each user’s holdings. This portfolio planning layer is still being built.
2

Request a swap quote

The routing layer obtains a quote through a supported swap aggregator. The quote supplies the transaction data needed to perform the swap.
3

Prepare the account calls

MyStacks prepares the approval and swap calls for the user’s account. The execution must fit the account’s delegated permission.
4

Sign and submit the execution

KMS signs the request using the session signing key. The MyStacks execution layer coordinates the authorised account calls. The selected execution path supports sponsored transactions.
5

Observe the result

The execution result and onchain receipts show whether the trade settled. A successful quote or submission alone does not mean the portfolio has changed.

​
Routing and execution have different jobs

The routing layer obtains quotes through supported swap aggregators. The execution layer carries out the authorised trades in each user’s account.

​
What is still open?

The production rebalance service still needs its scheduling and operation lifecycle. Detailed execution controls and the final account permissions remain under design. The pricing and fee model for sponsored execution is still being defined. The initial scope is individual account execution. Shared settlement and internal trade netting are outside that scope. This draft makes no guarantee that an entire portfolio rebalance is atomic.