Why do transactions sent by a channel account do not appear in the operations history for the source account?

Question

I'm currently writing an app that facilitates multi-sig transactions, and one of the issues we faced was the fact that to enable multiple transactions to be created and signed, we had to use channel accounts in order to avoid having the wrong sequence number for a transaction e.g If we created two transactions using the multi-sig accounts sequence number, we would fall into a sequencing issue if we submitted the second transaction before the first one.

This is working great, however when you get the operations for an account (e.g /accounts/{multi_sig_account_id}/operations) it doesn't show the operations from the transaction submitted using the channel account.

It's odd because the transaction shows up when I look get the transactions for the account ( /accounts/{multi_sig_account_id}/transactions ), however it's a not really a useful endpoint as it doesnt show information about each operation in the transaction.

Is this intended behaviour?

Answer 1

when you get the operations for an account (e.g /accounts/{multi_sig_account_id}/operations) it doesn't show the operations from the transaction submitted using the channel account.

I guess it's because you apply operations to the channel accounts, so neither of operations are applied directly to the "multi_sig_account". Therefore, such operations shouldn't be displayed by /accounts/{multi_sig_account_id}/operations endpoint. It's hard to tell without a context; a link to an example tx would be helpful.

however it's a not really a useful endpoint as it doesnt show information about each operation in the transaction.

Actually, you can retrieve operations from the transaction. Just convert envelope_xdr to the transaction object.

const tx = new StellarSdk.Transaction(envelope_xdr)
console.log(tx.operations)