API Access for MultiSig Wallet Setup

[jnnakhara]

Hi Everyone, I was looking for some help with regards to API authentication under a MultiSig wallet setup. I understand the primary method is to simply have access to a keypair file for the wallet (https://drift-labs.github.io/v2-teacher/#authentication) however I'm working with an MPC wallet which does not have direct raw access to the key pair.

So far the only other DEX I've dug into on this (Vertex Protocol) has an alternative authentication method where you generate a "Linked Signer" private key to sign on behalf of the multisig. In this setup the linked signer is able to perform any exchange action on behalf of the main account with the caveat that any withdrawals from the account can only be directed back to the original wallet.

I did not see anything in the Drift docs that describe a setup like this so checking if this kind of feature is not currently available?

[wphan]

drift's delegate user is a similar feature, a subaccount's delegate is allowed to trade/deposit to the original account (can be multi sig owned), but cannot withdraw.

The delegate can be set on the UI (overview > manage subaccounts > Set up delegate).
The delegate can also be set through the smart contract via the update_user_delegate instruction.

And for Solana multisig wallets, we've had users report success with the squads SquadX extension (https://squads.so/extension)

[jnnakhara]

Thanks very much for the reply wphan. I was able to follow the instructions and add a delegate wallet. The initial task I'm trying to accomplish is to actually just query the delegated account (simply see my balances and positions) via API access. I'm using the python SDK and initializing the client by referencing this input template: https://drift-labs.github.io/v2-teacher/?python#connection

My understanding is that (in addition to the default connection and wallet parameters) I need to specify the optional authority parameter with the public address of my delegated wallet (the one I'm trying to control with the newly added delegate). I only have one "Main Account" setup so I'm not specifying the activeSubAccountId parameter assuming it defaults to 0 as necessary. So generally I have:

drift_client = DriftClient(connection=connection, wallet=wallet, env='mainnet', authority='<MY_DELEGATED_ADDRESS>')

That said, when I try to call user = drift_client.get_user() I receive the error Error: KeyError: 'No sub account id 0 found'

Is there something I'm missing in the client initialization setup that's not anchoring it to the delegated address?

[0xbigz]

its possible you didnt initialize a user for this wallet yet?

https://drift-labs.github.io/v2-teacher/?python#user-initialization

[jnnakhara]

Thanks 0xbigz, I did not call the user-initialization step as I may have misunderstood the second note in the docs saying "Alternatively you can export the private key of an existing user that has been initialized via the UI. This will allow you to use the same user account programatically." What I think I'm misunderstanding is if the delegate account (the one I intend to control another account, i.e. the managed account) needed to have it's own subaccount setup independently, even if I wasn't trading in the delegate account.

In other words, ignoring API access, I was able to connect the delegate account to the UI and see the managed account visible with all the described features (able to view positions, deposit, trade) without previously creating a subaccount in the delegate. So naively I assumed that "initialization" was complete for my delegate account given the UI connect was working.

Is it correct that I need to go through the motions of creating a separate subaccount for the delegate before I can "control" the managed account with the API?