Hermes v0.4.4

This release has some fixes in Hermes and doesn't include any breaking change.

What's Changed

• feat(hermes): add uniqueness check for benchmark price by @ali-bahjati in #1122
• fix(hermes): handle price feed removal properly by @ali-bahjati in #1166

Full Changelog: hermes-v0.4.2...hermes-v0.4.4

xc-admin-v0.5.1

[xc-admin-proposer] Handle RPC errors (#1167)

* Fix server

* Add some comments

Pyth EVM Contract v1.3.3

Changes

Added support for Stacks chain in governance

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. Use 200 for the optimizer runs option.

Pyth EVM Contract v1.3.2

Changes

This release includes the new function parsePriceFeedUpdatesUnique which can be used to check whether a price update is actually the first update within a time range.

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. Use 200 for the optimizer runs option.

xc-admin-v0.5.0

Update dockerfile (#1041)

* Update dockerfile

* Drive by v4

* Reduce scope

* Revert dockerfile

* Revert dockerfile changes

* Cleanup the other dockerfile

* Remove contracts dir

* Remove old cli

Pyth EVM Contract v1.3.1

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.

pyth-js-v13

What's Changed

• [sui] Use manual serialization for vaas by @m30m in #1016

pyth-js-v12

What's Changed

• [sui] Sui dx improvement by @m30m in #1011
• change waitForMaybeReadyWebSocket to 5 seconds by @cctdaniel in #1017

Full Changelog: pyth-js-v11...pyth-js-v12

pyth-js-v11

[Sui 21/x] - pyth-sui-js SDK (#1004)

* Add sui js sdk

* Update dependencies and package lock

---------

Co-authored-by: Amin Moghaddam <[email protected]>

Pyth Cosmwasm Contract v1.3.0

Contracts

• cosmwasm.zip contains the generic cosmwasm contract for most Cosmos SDK chains.
• injective.zip contains injective specific contract.
• osmosis.zip contains osmosis specific contract.