@hashgraph/hedera-wallet-connect 2.0.1-canary.5c580dd.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 +2 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -42,9 +42,7 @@ For more information see:
|
|
|
42
42
|
- [Ethereum JSON-RPC Specification ](https://ethereum.github.io/execution-apis/api-documentation/)
|
|
43
43
|
- [Hedera JSON-RPC relay](https://docs.hedera.com/hedera/core-concepts/smart-contracts/json-rpc-relay)
|
|
44
44
|
- [Hedera Native JSON-RPC spec for WalletConnect](https://docs.reown.com/advanced/multichain/rpc-reference/hedera-rpc)
|
|
45
|
-
- [
|
|
46
|
-
- [Reown Docs](https://docs.reown.com/overview)
|
|
47
|
-
- [WalletConnect Network](https://walletconnect.network/)
|
|
45
|
+
- [@hashgraph/sdk](https://www.npmjs.com/package/@hashgraph/sdk)
|
|
48
46
|
|
|
49
47
|
# Getting started
|
|
50
48
|
|
|
@@ -235,4 +233,4 @@ While minimal, the main breaking changes are:
|
|
|
235
233
|
|
|
236
234
|
- initially, a transaction created by the Hedera Javascript SDK needed to have one or more
|
|
237
235
|
consensus node ids set to be able to serialize into bytes, sent over a network, and
|
|
238
|
-
deserialized by the SDK
|
|
236
|
+
deserialized by the SDK.
|