@hyperlane-xyz/core 5.2.1 → 5.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -3,13 +3,13 @@
3
3
  ## Interchain Accounts
4
4
 
5
5
  An interchain account is a smart contract that is deployed on a remote chain controlled exclusively by the origin chain's deployer account.
6
- Interchain accounts provide developers with a [transparent multicall API](../OwnableMulticall.sol) to remote smart contracts.
6
+ Interchain accounts provide developers with a [transparent multicall API](libs/OwnableMulticall.sol) to remote smart contracts.
7
7
  This avoids the need to deploy application specific smart contracts on remote chains while simultaneously enabling cross-chain composability.
8
8
 
9
9
  See [IBC Interchain Accounts](https://github.com/cosmos/ibc/blob/main/spec/app/ics-027-interchain-accounts/README.md) for the Cosmos ecosystem equivalent.
10
10
 
11
11
  ## Interchain Query System
12
12
 
13
- The interchain query system generalizes view calls to contracts on remote chains. It is a [transparent multicall API](../OwnableMulticall.sol) that can be used to query remote smart contracts. This avoids the need to deploy application specific smart contracts on remote chains while simultaneously enabling cross-chain composability.
13
+ The interchain query system generalizes view calls to contracts on remote chains. It is a [transparent multicall API](libs/OwnableMulticall.sol) that can be used to query remote smart contracts. This avoids the need to deploy application specific smart contracts on remote chains while simultaneously enabling cross-chain composability.
14
14
 
15
15
  See [IBC Interchain Query System](https://github.com/cosmos/ibc/tree/main/spec/app/ics-031-crosschain-queries) for the Cosmos ecosystem equivalent.
@@ -45,9 +45,9 @@ graph LR
45
45
 
46
46
  The Token Router contract comes in several flavors and a warp route can be composed of a combination of these flavors.
47
47
 
48
- - [`Native`](./contracts/HypNative.sol) - for warping native assets (e.g. ETH) from the canonical chain
49
- - [`Collateral`](./contracts/HypERC20Collateral.sol) - for warping tokens, ERC20 or ERC721, from the canonical chain
50
- - [`Synthetic`](./contracts/HypERC20.sol) - for representing tokens, Native/ERC20 or ERC721, on a non-canonical chain
48
+ - [`Native`](./HypNative.sol) - for warping native assets (e.g. ETH) from the canonical chain
49
+ - [`Collateral`](./HypERC20Collateral.sol) - for warping tokens, ERC20 or ERC721, from the canonical chain
50
+ - [`Synthetic`](./HypERC20.sol) - for representing tokens, Native/ERC20 or ERC721, on a non-canonical chain
51
51
 
52
52
  ## Interchain Security Models
53
53
 
package/package.json CHANGED
@@ -1,11 +1,11 @@
1
1
  {
2
2
  "name": "@hyperlane-xyz/core",
3
3
  "description": "Core solidity contracts for Hyperlane",
4
- "version": "5.2.1",
4
+ "version": "5.3.0",
5
5
  "dependencies": {
6
6
  "@arbitrum/nitro-contracts": "^1.2.1",
7
7
  "@eth-optimism/contracts": "^0.6.0",
8
- "@hyperlane-xyz/utils": "5.2.1",
8
+ "@hyperlane-xyz/utils": "5.3.0",
9
9
  "@layerzerolabs/lz-evm-oapp-v2": "2.0.2",
10
10
  "@openzeppelin/contracts": "^4.9.3",
11
11
  "@openzeppelin/contracts-upgradeable": "^v4.9.3",