Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Hedera Network in WalletConnect Integration for Blade Wallet #4533

Closed
1 task done
adjuric-symphony opened this issue Feb 4, 2025 · 0 comments
Closed
1 task done

Comments

@adjuric-symphony
Copy link

adjuric-symphony commented Feb 4, 2025

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:

const NAMESPACE = 'eip155'

However, the Hedera network (per HIP-30) uses the hedera:<network> format, such as hedera:testnet or hedera: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 or hedera: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

@adjuric-symphony adjuric-symphony changed the title Support for Hedera Network by Updating Namespace in WalletConnect Support for Hedera Network in WalletConnect Integration for Blade Wallet Feb 4, 2025
@wevm wevm locked and limited conversation to collaborators Feb 11, 2025
@jxom jxom converted this issue into discussion #4541 Feb 11, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant