Um, actually, Ethereum is the name of the protocol, not the cryptocurrency You're thinking of "Ethereum's Monster"

@real_philogy yeah selfdestruct is always post-tx since that’s when the client can clean up the account state selfdestruct in the constructor itself should result in zero code at the address though, since it halts execution like return does

the null vs zero-length distinction is also important

@real_philogy ahh yes of course that too

@lovethewired that’s if you use selfdestruct - my q was about empty bytecode in particular as an alternative (but it doesn’t work)

isn’t cbor metadata the fastest way to notify projects about compiler vulnerabilities? and only insight into language + compiler version metrics for chains? it won’t change the bytecode unless you change solc version (which will probably change the bytecode) right? so including is harmless for deterministic deploys

@gndizzy @merkleplant_eth @zerosnacks good note about inline config, haven’t had a chance to use that yet. also good reminder that even in fork tests you need to explicitly set evm version :(

@merkleplant_eth @zerosnacks forge fork test as part of ci could catch incompatibilities when adding new chains/rpcs automatically at least still needs eng lift to support the incompatible ones vs just managing signing keys though, i can see that being a pain point

@merkleplant_eth @zerosnacks do you think the worry is that people will deposit on the wrong chain? otherwise doesn’t really matter if contract is simple even if bytecode changes right?

@zerosnacks interesting. skill issues afaict

my skepticism around berachain is based on the fact that if it were a good idea uniswap would at least be exploring it

interesting - repos being spammed by AI PRs maybe try committing a “robots.txt” that’s just 1m+ tokens of lorem ipsum

@CupOJoseph the destination smart contract nonce gets incremented by create/2 per eip-161 bc clients were purging smart contracts as they were being created bc they had 0 code and 0 nonce and looked uninitialize lol

pls leave selfdestruct alone i need it @ethereum

@CupOJoseph selfdestruct is still allowed in same tx so it’s still useful for some things but since nonce is incremented for duration of tx can’t do it multiple times in a tx

@0xKaden yeah just want to avoid paying for bytecode, selfdestruct the only way i guess

@CupOJoseph yeah was trying to see if there was a way to avoid selfdestruct, guess not but can only selfdestruct once per tx so would need to use a bundler not important tho just want to avoid bytecode costs

i believe at minimum the account gets “initialized” and it’s extcodehash changes but that’s true if you seed a counterfactual account with ether too