@chriseth Regarding yesterday's conclusion about storing constructor arguments for all contracts and not just for those using immutables, here are some thoughts:
With the current implementation, we would sacrifice user experience in order to store constructor arguments for every contract - and the values used for initialization might later be overwritten. So, at least for now, should we just keep the storing of constructor arguments only for contracts that use immutables?
Just dropping this here: https://github.com/tintinweb/smart-contract-sanctuary
A home for ethereum smart contracts verified on Etherscan.
Note: This repo is updated twice a day.
I know that due to uncertainty about licensing it may not make sense importing it into sourcify, but still.