Skip to main content
MyStacks separates portfolio decisions from asset ownership. The backend coordinates the work. Each user’s smart account holds their assets and governs delegated execution.

​
System map

MyStacks architecture. Manager portfolio decisions and user requests reach the backend. Liquidity routing supplies swap quotes. KMS signs session requests for the MyStacks execution layer. Each user's smart account holds the assets and enforces delegated permissions. The owner retains authorisation, revocation, and withdrawal control. The arrows describe responsibilities and transaction flow.

​
Account layer

Each user’s portfolio sits in a user-owned smart account. The account keeps ownership separate from permission to trade. Delegated permissions allow MyStacks to carry out authorised portfolio operations. Read smart accounts and ownership for the user and manager boundary.

​
Coordination layer

MyStacks connects subscriptions and portfolio decisions to transaction execution. The backend coordinates these operations for each user’s smart account.

​
Execution layer

Liquidity routing connects portfolio trades to supported swap aggregators. The MyStacks execution layer coordinates the resulting account calls. The selected path supports sponsored transactions. KMS, a key management service, protects the session signing key and signs execution requests. This signing capability is separate from the user’s ownership key. Read execution and rebalancing for the flow from quote to confirmation.