Charles Cooper

:+1: for this I guess while this is still being implemented, a workaround is to use a temp table in conjunction with copy. Something like this: ```python async with conn.transaction():...

this was a bug in vyper's source map output, fixed in https://github.com/vyperlang/vyper/pull/2691

@Ippolo closing, please reopen if still an issue

i did a bit of investigation, and it looks like there are two issues here. the ERC20.vy contract has assertions with no reason string, e.g. ```vyper assert msg.sender == owner...

solidity has metadata in the bytecode, but it gets stripped here: https://github.com/eth-brownie/brownie/blob/ef0d5af3bb48edcd11abf985626fc99dbc577c7d/brownie/project/compiler/solidity.py#L257-L268 so i guess maybe the most kosher way to fix this is for vyper to publish the layout...

i opened https://github.com/vyperlang/vyper/pull/2768 in the vyperlang repository to publish the immutables layout file. but i realized a simpler way for brownie to do this is to request both `bytecode` and...

should be fixed as of https://github.com/eth-brownie/brownie/pull/1623. @scherrey please reopen if still an issue

@iamdefinitelyahuman maybe a good path forward could be if you add another owner to the brownie repository who is able to carry on maintenance+development?

> someone like you? @charles-cooper ? @poolpitako i appreciate the vote of confidence! i definitely have my hands full with vyper right now so i don't think i could be...

one interesting thing i realized while chatting with @esaulpaugh is that "calldata" is comparatively cheaper for inter-contract calls. so it might be worth having a more compressed encoding for calldata...