LinearERC20Voting is deployed to Mainnet and Polygon.
A tiny change is made to a comment in the LinearERC20Voting.sol source file.
LinearERC20Voting is deployed to all the other chains.
What this means, is that when running the deployment system against mainnet or polygon, it will deploy LinearERC20Voting (and LinearERC20WrappedVoting which inherits), due to that small difference, the system is technically correct that this version of the contract doesn't exist on that chain and so it should be deployed.
I just added some early exits to the deployment script, to skip these contracts on mainnet and polygon. I've also added the original contract for posterity.
It would be nice to just deploy the updated version to mainnet and polygon and publish these new master copy addresses, but I don't think there will be some bad bugs in the frontend if we did that.
AFAIK we're stuck with our current implementation address, at least until we build some more concepts of versioning the master copy contracts into our systems here.
Timeline of events:
LinearERC20Votingis deployed to Mainnet and Polygon.LinearERC20Voting.solsource file.LinearERC20Votingis deployed to all the other chains.What this means, is that when running the deployment system against mainnet or polygon, it will deploy
LinearERC20Voting(andLinearERC20WrappedVotingwhich inherits), due to that small difference, the system is technically correct that this version of the contract doesn't exist on that chain and so it should be deployed.I just added some early exits to the deployment script, to skip these contracts on mainnet and polygon. I've also added the original contract for posterity.
It would be nice to just deploy the updated version to mainnet and polygon and publish these new master copy addresses, but I don't think there will be some bad bugs in the frontend if we did that.
AFAIK we're stuck with our current implementation address, at least until we build some more concepts of versioning the master copy contracts into our systems here.