Support for Hedera Network in WalletConnect Integration for Blade Wallet #4541
Unanswered
adjuric-symphony
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Check existing issues
Describe the bug
Description
When using WalletConnect with wagmi, Blade Wallet is listed as an option. It only seems to allow connections to Ethereum Mainnet and Sepolia, with no option available for the Hedera network.
The current implementation uses the eip155 namespace by default, which is only compatible with Ethereum-based chains:
wagmi/packages/connectors/src/walletConnect.ts
Line 104 in 5275810
However, the Hedera network (per HIP-30) uses the
hedera:<network>
format, such ashedera:testnet
orhedera:296
for the testnet. Currently, this results in Blade Wallet only connecting to Ethereum Mainnet or Sepolia, with no option for the Hedera network.Proposed Change
To make the WalletConnect integration with Hedera work seamlessly, I propose updating the default namespace to include a configurable namespace option (e.g., hedera). Specifically, the chain ID for Hedera should follow the format
hedera:<network>
.For example:
For Hedera Testnet:
hedera:testnet
orhedera:296
This would align with the standard HIP-30 and allow for proper connectivity to the Hedera network in Blade Wallet.
Additional Notes:
It would be great if the session proposal logic could be updated to support multiple namespaces (e.g., eip155, hedera) and allow users to specify the correct chain format for their network.
Link to Minimal Reproducible Example
No response
Steps To Reproduce
No response
What Wagmi package(s) are you using?
wagmi
Wagmi Package(s) Version(s)
2.14.9
Viem Version
2.22.21
TypeScript Version
5.7.3
Anything else?
No response
Beta Was this translation helpful? Give feedback.
All reactions