<BogdanHabic> I tried to flatten the folder structure, but then the imports don't work (as expected)
<edi-shardlabs> We can see it behaves like that sometimes. It would be awesome if you could also check in which browser and if it happens in incognito mode also.
<fabijan_shardlabs> @BogdanHabic We're checking your issue
<BogdanHabic> @fabijan_shardlabs there is a huge chance that it might be my code that is doing something wrong, but I cannot see what. Again, this is only for contracts that aren't in a flat directory structure, but since Etherscan started supporting solc standard json verification, we tend to see a lot of these around
<darko> @bunsenstraat I just tested it, it works in chrome for me but fails to download in firefox. This might be an issue with remix iframe sandbox not having
allow-downloads enabled, 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
<darko> I left a comment in the issue ethereum/remix-plugins-directory#172
<edi-shardlabs> @BogdanHabic btw it would be great if you have more (which you for sure have) examples that we can test on, so we are sure that fix is working properly.
<BogdanHabic> > @BogdanHabic btw it would be great if you have more (which you for sure have) examples that we can test on, so we are sure that fix is working properly.
@edi-shardlabs If you want, I can run the import and then deliver to you all of the contracts that weren't verified successfully. Would that work?
@edi-shardlabs If you want, I can run the import and then deliver to you all of the contracts that weren't verified successfully. Would that work?
<BogdanHabic> This service won't generate a lot of load, as there aren't a lot of verifications per day
<BogdanHabic> > @BogdanHabic How do you set the compilationTarget property in the metadata provided above (referring to the post body file)?
@fabijan_shardlabs There was a mistake on my side in some cases when I was generating the compilationTarget property. I pushed out a fix for it and we're collecting successful/unsuccessful verification now 😄
@fabijan_shardlabs There was a mistake on my side in some cases when I was generating the compilationTarget property. I pushed out a fix for it and we're collecting successful/unsuccessful verification now 😄
<edi-shardlabs> It's maintainance of the server in Berlin office 😦
<edi-shardlabs> There is a backup service
<edi-shardlabs> https://server.verificationstaging.shardlabs.io/
<edi-shardlabs> 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)
<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?
<edi-shardlabs> It's setup as two different services, I don't have control over that server in Berlin and this is what we run on our own infrastracture, so it's not currently connected.
<edi-shardlabs> Maybe trying in couple of hours would be best 🙂
<yann300> would be great to get your feedback on the plugin dev experience, if you have time for a call one of these days.
<BogdanHabic> Regarding this, sure thing! I think it would be best to have the call early next week, so I can wrap everything on my side regarding my plugin and gather my thoughts
<BogdanHabic> Are you available on Tuesday?
I'm interested in learning more about creating Remix plugins. Basically, I'm tired of all the woes from testing projects with OpenZeppelin contracts, and I would like to see how hard it would be to architect a plugin that has the contracts, bonus points if imports like
@openzeppelin/contracts/token/ERC20/ERC20.sol work without needing to reroute them.
I'm looking through the README, but don't really understand what I would need to do to start building this. Is it possible for someone to help me get started, and evaluate how much time and effort this would take.
@bunsenstraat
(like me, just I miss it when people @ me too)
@wschwab so if you tell what you’d need to do I can point you to some relevant docs
The bonus would be if it could be done in a way that the standard npm package import people usually code with would work (eg
@openzeppelin/contracts/token/ERC20/ERC20.sol). The internal strcuture seems easy enough, the question is if there's any way to make the @openzeppelin to work (instead of something like ./openzeppelin)
yes, that could be possible... I m a bit unsure how to map openzeppelin to @openzeppelin but i m sure we can find something.
ccing @EdsonAlcala who is the developer of the defi plugin.
also if you use remixd or remix-desktop https://github.com/ethereum/remix-desktop importing with @openzeppelin/contracts/token/ERC20/ERC20.sol should already work
I'm looking at the DeFi plugin, and i have to admit I'm still confused about how to build plugins (in this case how to setup contracts to be deployed and recognized by the system).
I can make the leap that the
I can make the leap that the
/deployments folder in the Defi plugin are where the magic happens, but I don't really get what I need to do.