Skip to main content

MyStacks

Portfolio infrastructure for tokenised finance. It uses per-user smart accounts to separate user ownership from delegated portfolio activity.

Portfolio

The assets held in a user’s smart account. Each portfolio follows the model defined by its subscribed strategy.

Strategy

The manager’s model portfolio of assets and target weights. Multiple users can follow the same strategy while holding their assets separately.

Manager

The party that chooses a strategy’s assets and target weights. A change to those weights applies at the next scheduled rebalance. A manager has no withdrawal authority under the intended product model.

Subscription

A user’s enrolment in a strategy. It connects the user’s portfolio to the manager’s allocation model.

Smart account

A per-user account that holds assets and supports delegated execution. The user retains ownership and can revoke automation or withdraw assets.

Delegated permissions

Authority that a user grants for defined portfolio operations. The user can revoke these permissions without giving up account ownership.

Session signer

A signer used to authenticate requests allowed by delegated permissions. It acts within a session and does not own the user’s smart account.

KMS

A key management service that protects the session signing key and signs requests. It does not give MyStacks ownership of the user’s account.

Rebalance

A set of swaps intended to move a user’s holdings towards a portfolio’s target allocation. The planned execution workflow applies manager allocation updates at the next applicable schedule boundary. The Manager API defines the accepted schedule presets. Automated scheduled trading is still being built.

Swap aggregators

Services that provide swap quotes and route data for portfolio transactions. MyStacks passes selected quotes into its execution flow.

Execution layer

The MyStacks layer that coordinates and submits portfolio transactions. It works from routes selected using swap aggregator quotes.