@hashgraph/hedera-wallet-connect 2.0.1-canary.619d02d.0 → 2.0.1-canary.6be69a2.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 +11 -11
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,11 +1,10 @@
|
|
|
1
1
|
# Background
|
|
2
2
|
|
|
3
|
-
## Overview
|
|
4
|
-
|
|
5
3
|
This library provides tools and recommendations on how to integrate Hedera into an application
|
|
6
4
|
that requires communication with a wallet that supports Hedera. There are 2 different paths to
|
|
7
5
|
integrate Hedera in this context. Both approaches use the
|
|
8
|
-
[WalletConnect](https://walletconnect.network/) network to send messages from apps to wallets
|
|
6
|
+
[WalletConnect](https://walletconnect.network/) network to send messages from apps to wallets
|
|
7
|
+
and back.
|
|
9
8
|
|
|
10
9
|
## Hedera APIs
|
|
11
10
|
|
|
@@ -23,9 +22,9 @@ Hedera gRPC and REST API calls.
|
|
|
23
22
|
## Ethereum JSON-RPC vs. Hedera JSON-RPC vs. Hedera JSON-RPC Relay
|
|
24
23
|
|
|
25
24
|
When integrating, app developers can choose to use the Hedera native approach and send
|
|
26
|
-
transactions to wallets over the WalletConnect
|
|
27
|
-
native transactions or use Ethereum JSON-RPC calls sent to a Hedera JSON-RPC Relay
|
|
28
|
-
which then communicates with Hedera consensus and mirror nodes.
|
|
25
|
+
transactions to wallets over the WalletConnect network using the JSON-RPC spec defined for
|
|
26
|
+
Hedera native transactions or use Ethereum JSON-RPC calls sent to a Hedera JSON-RPC Relay
|
|
27
|
+
provider which then communicates with Hedera consensus and mirror nodes.
|
|
29
28
|
|
|
30
29
|
On a high level, JSON-RPC is a type of API stucture, such as SOAP, gRPC, REST, GraphQL, etc. In
|
|
31
30
|
the Hedera ecosystem, there are distinct concepts regarding JSON-RPC APIs to consider:
|
|
@@ -51,13 +50,14 @@ In addition to choosing between the Hedera native JSON-RPC spec and the Ethereum
|
|
|
51
50
|
when building with javascript/typescript, there are 2 supported options to utilize the
|
|
52
51
|
WalletConnect network to send information from apps to wallets and back.
|
|
53
52
|
|
|
54
|
-
This README assumes
|
|
53
|
+
This README assumes an understanding of Hedera as well as the WalletConnect network and focusses
|
|
55
54
|
on how to send a payload to a wallet for processing and presentation to an end user that is a
|
|
56
55
|
Hedera account holder. We recommend reviewing the [Hedera Docs](https://docs.hedera.com/) and
|
|
57
56
|
first submitting transactions directly to the Hedera network without requiring interaction with
|
|
58
|
-
a [Wallet](#hedera-wallets) when integrating Hedera for the first time.
|
|
57
|
+
a [Wallet](#hedera-wallets) when integrating Hedera for the first time. We also recommend
|
|
58
|
+
reviewing the [Reown docs](https://docs.reown.com/overview).
|
|
59
59
|
|
|
60
|
-
## Using this library and WalletConnect libraries directly
|
|
60
|
+
## Using this library and underlying WalletConnect libraries directly
|
|
61
61
|
|
|
62
62
|
1. Add Hedera dependencies to your project:
|
|
63
63
|
|
|
@@ -231,6 +231,6 @@ While minimal, the main breaking changes are:
|
|
|
231
231
|
|
|
232
232
|
- remove setting node id's within this library for transactions
|
|
233
233
|
|
|
234
|
-
- initially, a transaction created by the Hedera
|
|
235
|
-
|
|
234
|
+
- initially, a transaction created by the Hedera Javascript SDK needed to have one or more
|
|
235
|
+
consensus node ids set to be able to serialize into bytes, sent over a network, and
|
|
236
236
|
deserialized by the SDK.
|