The latest updates on your projects. Learn more about Vercel for Git ↗︎

I was able to successfully upgrade the contract using a local anvil. Will attempt to upgrade the actual contract tomorrow.

Performed the following test which succeeded:

1. Reverted to main and deployed contract (took about 2M gas)
2. Added trusted signer (Same one in the unit test)
3. Switched to this branch
4. Updated migrate call to also call the below code after its original upgrade code

vm.startBroadcast();
        PythLazer lazer = PythLazer(payable(proxyAddress));
        bytes
            memory update = hex"2a22999a577d3cc0202197939d736bc0dcf71b9dde7b9470e4d16fa8e2120c0787a1c0d744d0c39cc372af4d1ecf2d09e84160ca905f3f597d20e2eec144a446a0459ad600001c93c7d3750006240af373971c01010000000201000000000005f5e100";
        lazer.verifyUpdate{value: 1}(update);
        vm.stopBroadcast();

5. Verified that the verifyUpdate function succeeds
6. Called verifyUpdate with no fee attached and received expected revert Error

So, it seems we are able to carry over the previous signature and correctly validate with it still, as well as expect the fee.

Contract was upgraded successfully. Merging.
Proxy Address: https://sepolia.etherscan.io/address/0xACeA761c27A909d4D3895128EBe6370FDE2dF481