TransactionResponse contains different sender/receiver to the TransactionDescription

Describe the bug

I instantiated a contract object called getTransaction which returns a TransactionResponse object that contains a data key and a to field. The docs say that TransactionResponse inherits from Transaction which has a to field that’s the receiver of a transaction.

The confusion for me is when I decode the data key of the TransactionResponse I get a TransactionDescription object that also contains a to field. But the to field from the TransactionResponse does not match the to field from the TransactionDescription match and I’ve been trying to understand why.

Reproduction steps

const url = 'cannot-include-for-security-reasons-replace-with-quiknode'
const ethers = require("ethers");
const utils = ethers.utils

const init = function() {
    const provider = new ethers.providers.WebSocketProvider(url);
    provider.on('pending', (tx) => {
        provider.getTransaction(tx).then(function(transaction) {
            const decodedInput = inter.parseTransaction({
                data: transaction.data,
                value: transaction.value
            });

            const transactionResponseReceiver = transaction.to;
            const transactionDescriptionReceiver = decodedInput.args.to

            console.log(transactionResponseReceiver)
            console.log(transactionDescriptionReceiver)

            console.log(transactionResponseReceiver === transactionDescriptionReceiver)
        });
    });
}

init();

Environment: Node: v14.15.4 Mac: Big Sur version 11.2.3 (20D91)

Search Terms TransactionDescription receiver and TransactionResponse

[fomotrader]

Will certainly do and again thank you for maintaining this library and being so kind as to help out a lost beginner

[ricmoo]

There is only 1 to for a transaction. But a Contract can be anything. So it sounds like the contract you are interacting with has a to (completely unrelated to the transaction) as a parameter to a function call. I won’t know more without more data.

But these questions also make more sense as a discussion. The issues are more for bugs and feature requests. 😃