This is an example wallet that integrates Hedera using both the native Hedera gRPC and REST APIs as well as Ethereum JSON-RPC compatible endpoints. This app utilizes Reown WalletKit. For an example Hedera app implementation see https://github.com/hgraph-io/hedera-app.
Note
Hedera consensus nodes provide gRPC APIs to change network state such as submitting as transferring cryptocurrency or smart contract calls that change network state.
Hedera mirror nodes provide REST APIs to query read-only network state such as account balances and transaction history.
- Fill out the .env file with a Reown project id.
## copy and then update the .env file
cp .env.example .env
- Install dependencies
npm install
- Run the app
npm run dev
The Hedera network provides gRPC and REST APIs that are consumed by Hedera SDKs and network users.
Hedera supports the Ethereum JSON-RPC spec through a middle layer called the Hedera JSON-RPC Relay. This relay is responsible for translating Ethereum JSON-RPC compatible API calls into Hedera gRPC and REST API calls. To see a full list of supported methods, refer to the JSON-RPC Relay documentation linked in the note above.
Apps and wallets that integrate Hedera can choose to use the Hedera JSON-RPC Relay to interact with the network, directly use Hedera APIs and SDKs, or do both. A strong reason to leverage the Hedera JSON-RPC Relay is to utilize existing tools and libraries available in the EVM ecosystem such as Wagmi, Viem, AppKit, and WalletKit.
Warning
When using the EVM namespace, Hedera accounts that have Ed25519 public/private key pairs are not supported. See the docs for more information.
A strong reason to integrate Hedera via the native APIs is to fully support all account types and native transaction types provided by Hedera.
In the context of Reown's WalletKit and AppKit, this is defined by the namespaces requested by
apps to wallets. The namespace is eip155
for the EVM compatibility layer and hedera
for
native integration.