Bug and/or ambiguity in filtering events

[samtay]

documentation issue

In Ethers v6 / Getting started / Contracts / Listening to Events you define:

abi = [
  "event Transfer(address indexed from, address indexed to, uint amount)"
]
...
// Listen for any Transfer to "ethers.eth"
filter = contract.filters.Transfer("ethers.eth")
contract.on(filter, (from, to, amount, event) => {
  // `to` will always be equal to the address of "ethers.eth"
});

isn't that filter actually listening for transfers from "ethers.eth"? Also, other areas of the documentation and discussion here suggest that filter = contract.filters.Transfer(null, "ethers.eth") is the proper way to create this filter. What are the semantics of the various shape of arguments accepted by the filter?

my issue

I can't seem to get the listener arguments working for the following event:

const ABI = [
  'event TransferOccurred(bytes32 indexed senderPkHash, bytes32 indexed receiverPkHash)',
];
...
const filter = state.contract.filters.TransferOccurred(null, state.account);
state.contract.on(filter, (from, to) => {
    # here to is undefined and from looks like the event payload
}
state.contract.on(filter, (from, to, evt) => {
    # here to and evt are both undefined and from looks like the event payload
}

Is there something special about bytes32 in that these can't be decoded into the arguments of the listener?

[ricmoo]

Oh yes! That is a mistake in the example. It is listening to transaction from "ethers.eth". I'll update that.

Your code example looks fine. Can you console.log the state.account?

[samtay]

Sure: account: 0x9c8e5dee21c1648ff1e86bb9ec5033b0de34f5a70442e5c00bc9f59f4e9a34fb

[ricmoo]

Thanks. :)

Just checking, often people have a typo in their object, or its pulled from a .env or such and has empty (undefined) properties.

I'll try out a quick example of this today. What network are you on?

[samtay]

Oh it's a local node running Anvil - and that Anvil instance is customized but it is largely ethereum compatible (only difference is a few extra precompiles). So if there is an issue, it should be visible when connected to any ethereum testnet / mainnet.