ABI coder fails to process Vyper-generated tuples

Ethers Version

5.4.0

Search Terms

tuple abi vyper

Describe the Problem

When using structs in external functions in the latest Vyper release (0.3.3), the resulting ABI causes ethers to error out when attempting to encode data for them.

I provide snippets for an example of a constructor that fails in such a way.

Code Snippet

struct MyStruct:
    bar: address
    baz: address
    qux: int256
    qyz: uint256
    bazoo: uint256
    ka: uint256

@external
def __init__(foo: MyStruct[10]):

Contract ABI

{
  "stateMutability": "nonpayable",
  "type": "constructor",
  "inputs": [
    {
      "name": "foo",
      "type": "(address,address,int256,uint256,uint256,uint256)[10]"
    },
  ],
  "outputs": []
}

Errors

Error: invalid type (argument="type", value="(address,address,int256,uint256,uint256,uint256)", code=INVALID_ARGUMENT, version=abi/5.4.0)

Environment

node.js (v12 or newer), Hardhat

Environment (Other)

Vyper

[ricmoo]

Yes, looks like that bug exactly. 😉

My guess is they aren’t using the same ABI generation functions for outputs and inputs, as outputs seem to be correct.

In the meantime, you can write the human-readable ABI to get your code up an running until the compiler is fixed to generate the correct ABI for inputs. Or you can write the JSON ABI, but that’s so much more involved. 😃

const ABI = [
  // You first example with the constructor
  "constructor (tuple(address bar, address baz, int256 qux, uint256 qyz, uint256 bazoo, uint256 ka)[10] foo)",
];

[ricmoo]

This looks like it was fixed in Vyper. I’m going to close this now, but please let me know if there are still any problems. 😃