Richard Moore

I think it's because your return type is `(Validator[] calldata validators, PageResponse calldata pageResponse)`, which has 2 values. So (I think?) what you would really want is `const [ validators,...

Everything should be kosher with Array types now, as of [v6.13.0](https://github.com/ethers-io/ethers.js/releases/tag/v6.13.0). Let me know if you have any more issues. Thanks! :)

Aiya. I’ll look into it first thing in the morning. :s

@andrevmatos The objects returned are fully populated. The problem you are seeing is a limitation of `console.log`, but if a function returns a tuple, it is a [Result instance](https://docs.ethers.org/v6/api/abi/#Result). You...

Yes. I agree. With the `exports` available in modern node, it is also easy to do in a way that doesn't pollute the global namespace. This is definitely on my...

That is one of the reasons for moving the buckets from the contract to the methods in v6, so it can be backwards compatible to add new buckets. I’ll research...

A Signer should also have a `getAddress()` async function; what is the error you are getting? But the OP was about contracts, I which is unrelated.

That is how `tx = await contract.func()` works; returning once the transaction is in the mempool. Calling `await tx.wait()` will then wait for it to be mined, resolving to the...

What network are you on? Since ethers needs to lookup the tx from the mempool, this can happen on networks (or backends) which do not return transactions in the mempool.

I've contacted MetaMask to find out more about any recent changes. :)