@@ -13,7 +13,7 @@ read transactions. Hedera implements EVM compatible smart contracts using
1313[ Hyperledger Besu] ( https://besu.hyperledger.org/ ) under the hood.
1414
1515Ethereum developers and toolsets often expect to interact with Ethereum compatible chains using
16- the [ Ethereum JSON-RPC] ( https://ethereum.org/en/developers/docs/apis/json-rpc/ ) . To acheive
16+ the [ Ethereum JSON-RPC] ( https://ethereum.org/en/developers/docs/apis/json-rpc/ ) . To achieve
1717compatibility with this API,
1818[ Hedera JSON-RPC Providers] ( https://docs.hedera.com/hedera/core-concepts/smart-contracts/json-rpc-relay#community-hosted-json-rpc-relays )
1919operate a software middlelayer that translates Ethereum JSON-RPC compatible API calls into
@@ -26,15 +26,15 @@ transactions to wallets over the WalletConnect network using the JSON-RPC spec d
2626Hedera native transactions or use Ethereum JSON-RPC calls sent to a Hedera JSON-RPC Relay
2727provider which then communicates with Hedera consensus and mirror nodes.
2828
29- On a high level, JSON-RPC is a type of API stucture , such as SOAP, gRPC, REST, GraphQL, etc. In
29+ On a high level, JSON-RPC is a type of API structure , such as SOAP, gRPC, REST, GraphQL, etc. In
3030the Hedera ecosystem, there are distinct concepts regarding JSON-RPC APIs to consider:
3131
3232- Ethereum JSON-RPC spec defines how to interact with Ethereum compatible networks
3333- Hedera JSON-RPC Relay implements the Ethereum JSON-RPC spec for Hedera
3434- Wallets in the Hedera ecosystem also support a separate specification that defines how to send
3535 transactions and messages to wallets over the WalletConnect network without relying on a
3636 Hedera JSON-RPC Relay provider. This is a Hedera specific specification defined for utilizing
37- the WalletConnect network distict from other JSON-RPC specs such as the one defined by the
37+ the WalletConnect network distinct from other JSON-RPC specs such as the one defined by the
3838 Ethereum network.
3939
4040For more information see:
@@ -64,7 +64,7 @@ reviewing the [Reown docs](https://docs.reown.com/overview).
64641 . Add Hedera dependencies to your project:
6565
6666``` sh
67- npm install @hashgraph/hedera-wallet-connect@2.0.0 -canary.811af2f .0 @hashgraph/sdk @walletconnect/modal
67+ npm install @hashgraph/hedera-wallet-connect@2.0.4 -canary.3ca04e9 .0 @hashgraph/sdk @walletconnect/modal
6868```
6969
70702 . Initialize dApp Connector
@@ -121,7 +121,7 @@ await dAppConnector.openModal()
1211212 . Add Hedera dependencies to your project:
122122
123123``` sh
124- npm install @hashgraph/hedera-wallet-connect@2.0.1 -canary.24fffa7 .0 @hashgraph/sdk @walletconnect/universal-provider
124+ npm install @hashgraph/hedera-wallet-connect@2.0.4 -canary.3ca04e9 .0 @hashgraph/sdk @walletconnect/universal-provider
125125```
126126
1271273 . Update ` createAppKit ` with adapters and a universal provider for Hedera. Note the
@@ -154,7 +154,7 @@ const hederaEVMAdapter = new HederaAdapter({
154154})
155155
156156const universalProvider = (await HederaProvider .init ({
157- projectId: " YOUR_PROJECT_ID"
157+ projectId: " YOUR_PROJECT_ID" ,
158158 metadata ,
159159})) as unknown as UniversalProvider , // avoid type mismatch error due to missing of private properties in HederaProvider
160160
@@ -215,7 +215,6 @@ createAppKit({
215215
216216- [ Hashpack] ( https://hashpack.app/ )
217217- [ Kabila] ( https://wallet.kabila.app/ )
218- - [ Blade] ( https://bladewallet.io/ )
219218- [ Dropp] ( https://dropp.cc/ )
220219
221220# Upgrading from v1 to v2
0 commit comments