El De-dog-lo

this seems kinda useful actually, suggest updating docs?

If we add `vyper_git_version.txt` to source control, it will change the commit hash to something other than the contents of that file. Sort of a chicken-egg issue. The correct resolution...

> ```vyper > from ethereum.ercs import IERC20 > > @external > def do_transfer(token: IERC20, receiver: address, amount: uint256, sig: Bytes[97]): > authorize(addr, sig) > authcall token.approve(receiver, amount) > authcall token.transfer(receiver,...

> ```vyper > token = authorize(address, sig) > # "token" is a compile-time concept which gets erased at runtime > # it is invalidated at compile-time if any other call...

> > ```vyper > > token = authorize(address, sig) > > # "token" is a compile-time concept which gets erased at runtime > > # it is invalidated at compile-time...

New constants and stuff like this would be great for namespacing in the standard library e.g. `from crypto.secp256k1 import CURVE_ORDER` or something (containing other types and functions like `.derive_public_key(Signature) ->...

That is my preferred outcome as well. Just use the filename (minus the extension) as the contract name for compatibility.

Also, this may not need to be an VIP?

I see the issue, yes we will be implementing a custom parser and updating our AST nodes to be specific to Vyper, intead of the strange PyAST/VyAST hybrid we have...

Meeting notes: will explore refactoring our AST information so it is easier to work with.