network_id: count 1: 57715 3: 48373 4: 30329 5: 2907 42: 19574
<edi-shardlabs> It would be great to start with 100ish as sourcify.dev is running on komputing which is a bit crowded and can't be scaled as easily. Staging is a bit better on that front as it's running in AWS.
What I propose is to let us know when you start uploading (and would do 100 recompilations for the start) to see if they give full match. If they do we can more easily scale staging environment so it can take a bigger load on it and can recompile more contracts.
Master branch is running on komputing that has also a bunch of other stuff on it so I can't promise preformance unfortunatelly.
Let me know when you start tommorow with this so I can be support if anything goes wrong.
allow-downloadsenabled, after adding this manually when testing in firefox worked for me. It seems like this restriction is not enforced in some browser versions, i'm not sure tbh
<BogdanHabic> > There is a backup service
But they are completely seperated. Still you can test there as that one has all the features of sourcify.dev with some aditional features (staging branch of the project)
so it shouldn't be used as a fallback I guess?
@openzeppelin/contracts/token/ERC20/ERC20.solwork without needing to reroute them.