incorrect legacy transaction from value

[belopash]

Ethers Version

6.1.0

Search Terms

No response

Describe the Problem

The value of property from for the legacy transaction has incorrect value.
Expected 0xbb9Bf3b2207c51273959DC571e4E1f01fb3A0B8D, but got 0x1349a095F2A49967e7f7A9AA5654cE56Ccd942Df.
Worked in v5.7.0

Code Snippet

// 6.1.0
const tx = ethers.Transaction.from({
        to: '0x08716e418e68564c96b68192e985762740728018',
        nonce: 603,
        gasLimit: 489365n,
        gasPrice: 1000000000n,
        value: 0n,
        data: '0x7a93696a0000000000000000000000000000000000000000000000000000000000000000',
        type: 0,
        signature: {
            r: '0x934e9b41ca05ce6581f4ef6f3f1026b7d190e0e4d0ff63c9b91865beeeb52768',
            s: '0x32314ac16b0234e643a46de09e39e62e32568b9dcbbd677fbff1e22ed649fa70',
            v: 2606n
        },
    })
tx.from // "0x1349a095F2A49967e7f7A9AA5654cE56Ccd942Df"

// 5.7.0
const serializedTransaction = serialize(
        {
            to: '0x08716e418e68564c96b68192e985762740728018',
            nonce: 603,
            gasLimit: 489365n,
            gasPrice: 1000000000n,
            value: 0n,
            data: '0x7a93696a0000000000000000000000000000000000000000000000000000000000000000',
            type: 0,
        },
        {
            r: '0x934e9b41ca05ce6581f4ef6f3f1026b7d190e0e4d0ff63c9b91865beeeb52768',
            s: '0x32314ac16b0234e643a46de09e39e62e32568b9dcbbd677fbff1e22ed649fa70',
            v: 2606
        }
    )
const tx = parse(serializedTransaction)
tx.from // "0xbb9Bf3b2207c51273959DC571e4E1f01fb3A0B8D"

Contract ABI

No response

Errors

No response

Environment

node.js (v12 or newer)

Environment (Other)

No response

[ricmoo]

Thanks. I’ll look into this asap with the other tx bug.

[belopash]

Hey, any updates on this?

[ricmoo]

Yes, it’s fixed locally and I’m running my final tests on v6.2 because there were some bigger changes to how the Contract meta-class populates it’s callable Proxy entry points and I want to make sure it is completely backwards compatible.

I expect it to be out within a few hours. :)

[ricmoo]

This has been fixed in v6.2.0. Try it out and let me know.

[belopash]

Yes, works now, thanks! Great job