@hashgraph/hedera-wallet-connect 2.0.1-canary.91c2137.0 → 2.0.1-canary.ae071fe.0

package/README.md

@@ -22,9 +22,9 @@ Hedera gRPC and REST API calls.
 ## Ethereum JSON-RPC vs. Hedera JSON-RPC vs. Hedera JSON-RPC Relay
 
 When integrating, app developers can choose to use the Hedera native approach and send
-transactions to wallets over the WalletConnect relays using the JSON-RPC spec defined for Hedera
-native transactions or use Ethereum JSON-RPC calls sent to a Hedera JSON-RPC Relay provider
-which then communicates with Hedera consensus and mirror nodes.
+transactions to wallets over the WalletConnect network using the JSON-RPC spec defined for
+Hedera native transactions or use Ethereum JSON-RPC calls sent to a Hedera JSON-RPC Relay
+provider which then communicates with Hedera consensus and mirror nodes.
 
 On a high level, JSON-RPC is a type of API stucture, such as SOAP, gRPC, REST, GraphQL, etc. In
 the Hedera ecosystem, there are distinct concepts regarding JSON-RPC APIs to consider:
@@ -42,7 +42,9 @@ For more information see:
 - [Ethereum JSON-RPC Specification ](https://ethereum.github.io/execution-apis/api-documentation/)
 - [Hedera JSON-RPC relay](https://docs.hedera.com/hedera/core-concepts/smart-contracts/json-rpc-relay)
 - [Hedera Native JSON-RPC spec for WalletConnect](https://docs.reown.com/advanced/multichain/rpc-reference/hedera-rpc)
-- [@hashgraph/sdk](https://www.npmjs.com/package/@hashgraph/sdk)
+- [Hedera Javascript SDK](https://www.npmjs.com/package/@hashgraph/sdk)
+- [Reown Docs](https://docs.reown.com/overview)
+- [WalletConnect Network](https://walletconnect.network/)
 
 # Getting started
 
@@ -50,16 +52,14 @@ In addition to choosing between the Hedera native JSON-RPC spec and the Ethereum
 when building with javascript/typescript, there are 2 supported options to utilize the
 WalletConnect network to send information from apps to wallets and back.
 
-This README assumes a basic understanding of how to create transactions on Hedera as well as
-handling sessions, payloads, and other transport layer details on the WalletConnect network and
-focusses on how to send a payload to a wallet for processing and presentation to an end user
-that is a Hedera account holder. We recommend reviewing the
-[Hedera Docs](https://docs.hedera.com/) and first submitting transactions directly to the Hedera
-network without requiring interaction with a [Wallet](#hedera-wallets) when integrating Hedera
-for the first time. We also recommend reviewing the
-[Reown docs](https://docs.reown.com/overview).
+This README assumes an understanding of Hedera as well as the WalletConnect network and focusses
+on how to send a payload to a wallet for processing and presentation to an end user that is a
+Hedera account holder. We recommend reviewing the [Hedera Docs](https://docs.hedera.com/) and
+first submitting transactions directly to the Hedera network without requiring interaction with
+a [Wallet](#hedera-wallets) when integrating Hedera for the first time. We also recommend
+reviewing the [Reown docs](https://docs.reown.com/overview).
 
-## Using this library and WalletConnect libraries directly
+## Using this library and underlying WalletConnect libraries directly
 
 1. Add Hedera dependencies to your project:
 
@@ -233,6 +233,6 @@ While minimal, the main breaking changes are:
 
 - remove setting node id's within this library for transactions
 
-  - initially, a transaction created by the Hedera javascript SDK needed to have a node id or
-    set of node id's set to be able to serialize into bytes to be passed sent over a network and
-    deserialized by the SDK.
+  - initially, a transaction created by the Hedera Javascript SDK needed to have one or more
+    consensus node ids set to be able to serialize into bytes, sent over a network, and
+    deserialized by the SDK

package/dist/reown/adapter.js

@@ -28,7 +28,7 @@ export class HederaAdapter extends AdapterBlueprint {
     setUniversalProvider(universalProvider) {
         this.addConnector(new HederaConnector({
             provider: universalProvider,
-            caipNetworks: this.caipNetworks || [],
+            caipNetworks: this.getCaipNetworks() || [],
             namespace: this.namespace,
         }));
     }

package/dist/reown/providers/EIP155Provider.d.ts

@@ -1,5 +1,5 @@
 import { EventEmitter } from 'events';
-import Client from '@walletconnect/universal-provider/node_modules/@walletconnect/sign-client';
+import Client from '@walletconnect/sign-client';
 import { SessionTypes } from '@walletconnect/types';
 import { IProvider, SessionNamespace, RpcProvidersMap, RequestParams, Namespace } from '@walletconnect/universal-provider';
 declare class EIP155Provider implements IProvider {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hashgraph/hedera-wallet-connect",
-  "version": "2.0.1-canary.91c2137.0",
+  "version": "2.0.1-canary.ae071fe.0",
   "description": "A library to facilitate integrating Hedera",
   "repository": {
     "type": "git",
@@ -30,8 +30,8 @@
     "prettier:fix": "prettier --write ./src/"
   },
   "peerDependencies": {
-    "@hashgraph/sdk": "^2.61.0",
-    "@reown/appkit": "^1.7.1",
+    "@hashgraph/sdk": "^2.63.0",
+    "@reown/appkit": "^1.7.3",
     "@reown/walletkit": "^1.2.3",
     "@walletconnect/modal": "^2.7.0",
     "ethers": "^6.13.5"