This repository was archived by the owner on Dec 8, 2025. It is now read-only.
This repository was archived by the owner on Dec 8, 2025. It is now read-only.
Solana support #363
Description
Depends on reown-com/reown-rust#61
In addition to updating this dependency, Notify Server itself expects eip155 in a few places:
- https://github.com/WalletConnect/notify-server/blob/aa855db08304f10120246d7c0b1db3e11fccb455/src/model/types/account_id.rs#L50
- (Depends on the above assertion) https://github.com/WalletConnect/notify-server/blob/5b76303f552cd0646bd4d2b717235345e26a2659/src/utils.rs#L20
- https://github.com/WalletConnect/notify-server/blob/5b76303f552cd0646bd4d2b717235345e26a2659/migrations/20240111200929_unique_account_address.sql#L4
These restrictions are in-place partly as offensive programming and in order to get a generic address which can be treated agnostic to a specific chain. When supporting Solana we need to implement chain-agnostic support as well. This could be a good opportunity to:
- Remove the function index for address, in-favor of a new unique column that stores the address (regardless of chain)
- This would also make feat: seq implementation #273 easier
- Normalize to ERC-55 in the database (already normalized) and reject non-ERC-55 requests (Detect if there is ERC-55 non-compliance #364)
- Lookup using address column, and the address from the SIWE message rather than the computed account ID