@hashgraph/hedera-wallet-connect 2.0.1-canary.91c2137.0 → 2.0.1-canary.d08bdc5.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.
- package/README.md +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -22,7 +22,7 @@ Hedera gRPC and REST API calls.
|
|
|
22
22
|
## Ethereum JSON-RPC vs. Hedera JSON-RPC vs. Hedera JSON-RPC Relay
|
|
23
23
|
|
|
24
24
|
When integrating, app developers can choose to use the Hedera native approach and send
|
|
25
|
-
transactions to wallets over the WalletConnect
|
|
25
|
+
transactions to wallets over the WalletConnect network using the JSON-RPC spec defined for Hedera
|
|
26
26
|
native transactions or use Ethereum JSON-RPC calls sent to a Hedera JSON-RPC Relay provider
|
|
27
27
|
which then communicates with Hedera consensus and mirror nodes.
|
|
28
28
|
|
|
@@ -59,7 +59,7 @@ network without requiring interaction with a [Wallet](#hedera-wallets) when inte
|
|
|
59
59
|
for the first time. We also recommend reviewing the
|
|
60
60
|
[Reown docs](https://docs.reown.com/overview).
|
|
61
61
|
|
|
62
|
-
## Using this library and WalletConnect libraries directly
|
|
62
|
+
## Using this library and underlying WalletConnect libraries directly
|
|
63
63
|
|
|
64
64
|
1. Add Hedera dependencies to your project:
|
|
65
65
|
|