Why is a transaction's to property named to address and the from being named account?

[davidmurdoch]

From an newcomer's perspective this naming seems asinine to me. But I'm sure there is a good reason :-)

Just curious if its documented anywhere?

[jxom]

• The Transaction APIs have a to (not address)
• The Contract & Transaction APIs have account – we use account to be consistent with other non-tx APIs such as signing and account can be an object instance (not only an address).
• The Contract APIs have address from historical perspective (Wagmi v0), but we can probably alias to to.

[jxom]

Use type: 'legacy'

[davidmurdoch]

ah, thanks again. We had tried 0x0 and it looks like viem ignored and it and just used 0x2.

[jxom]

How did TypeScript not pick it up?

[davidmurdoch]

Its being added to a partially untyped legacy codebase in a helper class that interfaces between multiple provider interfaces depending on the test environment.

[davidmurdoch]

formatters is undefined by default, so type = "legacy" is ignored by sendTransaction

const { anvil } = require('viem/chains');

const walletClient = createWalletClient({
  chain: anvil,
  transport: http(`http://127.0.0.1:8545`),
});

walletClient.chain.formatters === undefined // true

so in viem/actions/wallet/sendTransaction.js the call to extract includes a format value of undefined.

const chainFormat = client.chain?.formatters?.transactionRequest?.format;
const format = chainFormat || transactionRequest_js_1.formatTransactionRequest;
const request = format({
  ...(0, extract_js_1.extract)(rest, { format: chainFormat }),
  accessList,

And in viem/utils/formatters/extract.js, if format is falsely no values from value_: are included:

function extract(value_, { format }) {
    if (!format)
        return {};

---

Do we just need to configure the walletClient with some additional params to get the type param working?