Updating existing dapp to use `openzeppelin-contracts` instead of `openzeppelin-solidity`

@abcoathup The issue we’re encountering is similar to this one, Are ERC20 tokens already GSN capable? I’m now realizing that many of the @openzeppelin/contracts inherit from Context.sol (hence why that’s being compiled and showing up in the Declaration Error). However, we’re not trying to make any of our contracts GSN recipients.

We’re simply upgrading to @openzeppelin/contracts from openzeppelin-solidity for stability - i.e., so our contracts don’t break unexpectedly when upgrading to a newer minor version.

Given we’re not planning on doing anything w/ GSN, should we continue to rely on openzeppelin-solidity instead @openzeppelin/contracts?

1 Like