Closed ligi closed 2 years ago
filename char substitution problem: https://twitter.com/alexberegszaszi/status/1428711708055461890
Maybe my expectation about sourcify is wrong, but to explain, the way I would use sourcify is to read the metadata from https://repo.sourcify.dev/contracts/full_match/<chainid>/<address>/metadata.json
and then try to download the files one-by-one at https://repo.sourcify.dev/contracts/full_match/<chainid>/<address>/sources/<hash or proper path as in metadata>
. (Of course I need to double check that the downloaded files match the hash.)
If the filenames, as presented in the metadata, can not be stored in sourcify without changes, then I can see two good options: 1) Having a sourcify translation map next to the metadata (i.e. sourcifymap.json) 2) Storing the files under their keccak256 hash
A potential third options is allowing a package, such as sources.tar
, to be downloadable which has unchanged paths.