Skip to content

Pyth EVM Contract v1.3.0
Compare
Choose a tag to compare
@ali-bahjati ali-bahjati released this 18 Jul 09:29
· 1160 commits to main since this release
pyth-evm-contract-v1.3.0
dcec1e9
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

What's Changed

  • Ethereum/parse price feed updates accumulators by @swimricky in #855
  • [eth] - optimize parse/updatePriceFeeds for gas & bytesize by @swimricky in #868
  • [ethereum] - charge updateFee per number of updates by @swimricky in #878
  • [eth]: add forward compatibility test for accumulator updateData by @swimricky in #884
  • [eth] more update/parsePriceFeed optimizations by @swimricky in #886
  • [eth] - optimize ReceiverMessages parseAndVerifyVM by @swimricky in #901
  • [eth] Add setWormholeAddress governance message by @ali-bahjati in #917
  • [eth] Finalize accumulator contract by @ali-bahjati in #960

Full Changelog: pyth-evm-contract-v1.3.0-alpha...pyth-evm-contract-v1.3.0

Verification

To verify the contracts, go to the network explorer for our contract. Our contract is a proxy and the actual implementation is deployed elsewhere. First start with verifying the proxy (our contract address) with the standard input JSON file. Upload the ERC1967Proxy-std-input.json file from this release artifacts and use solidity 8.9 as the compiler and click on verify. Once you verify this contract there is a "Read as Proxy" tab on the explorer which gives you the address of the implementation if it's not verified yet. Go to the implementation contract address and repeat the same verification with solidity 8.4 and PythUpgradable-std-input.json release artifact.

If the explorer doesn't support standard input json they use the merged files. For the ERC1967Proxy use the optimizer runs 200 and for the PythUpgradable it is 2000.

Contributors

ali-bahjati and swimricky
Assets 9
Loading