@hashgraph/hedera-wallet-connect 2.0.1-canary.1c9f580.0 → 2.0.1-canary.3ca89d4.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 +12 -10
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -22,9 +22,9 @@ 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
|
|
26
|
-
|
|
27
|
-
|
|
25
|
+
transactions to wallets over the WalletConnect relays using the JSON-RPC spec defined for Hedera
|
|
26
|
+
native transactions or use Ethereum JSON-RPC calls sent to a Hedera JSON-RPC Relay provider
|
|
27
|
+
which then communicates with Hedera consensus and mirror nodes.
|
|
28
28
|
|
|
29
29
|
On a high level, JSON-RPC is a type of API stucture, such as SOAP, gRPC, REST, GraphQL, etc. In
|
|
30
30
|
the Hedera ecosystem, there are distinct concepts regarding JSON-RPC APIs to consider:
|
|
@@ -50,12 +50,14 @@ In addition to choosing between the Hedera native JSON-RPC spec and the Ethereum
|
|
|
50
50
|
when building with javascript/typescript, there are 2 supported options to utilize the
|
|
51
51
|
WalletConnect network to send information from apps to wallets and back.
|
|
52
52
|
|
|
53
|
-
This README assumes
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
53
|
+
This README assumes a basic understanding of how to create transactions on Hedera as well as
|
|
54
|
+
handling sessions, payloads, and other transport layer details on the WalletConnect network and
|
|
55
|
+
focusses on how to send a payload to a wallet for processing and presentation to an end user
|
|
56
|
+
that is a Hedera account holder. We recommend reviewing the
|
|
57
|
+
[Hedera Docs](https://docs.hedera.com/) and first submitting transactions directly to the Hedera
|
|
58
|
+
network without requiring interaction with a [Wallet](#hedera-wallets) when integrating Hedera
|
|
59
|
+
for the first time. We also recommend reviewing the
|
|
60
|
+
[Reown docs](https://docs.reown.com/overview).
|
|
59
61
|
|
|
60
62
|
## Using this library and underlying WalletConnect libraries directly
|
|
61
63
|
|
|
@@ -232,5 +234,5 @@ While minimal, the main breaking changes are:
|
|
|
232
234
|
- remove setting node id's within this library for transactions
|
|
233
235
|
|
|
234
236
|
- initially, a transaction created by the Hedera javascript SDK needed to have a node id or
|
|
235
|
-
set of node
|
|
237
|
+
set of node id's set to be able to serialize into bytes to be passed sent over a network and
|
|
236
238
|
deserialized by the SDK.
|