feat: add Solaxy (SVM) provider to universal-provider

[Marcolist]

Description

This PR adds Solaxy (SVM) support to the WalletConnect Universal Provider.

• Introduces a new provider file solaxy.ts under providers/universal-provider/src/providers/
• Registers it in index.ts
• Implements SolaxyProvider using standard JSON-RPC with endpoint https://rpc.solaxy.io
• Provides full compatibility with Solana RPC methods (Sealevel VM compatible)
• Enables connection to Solaxy via CAIP-2 chain ID solaxy:1936682104

This addition extends WalletConnect’s multichain support to the Solaxy ecosystem.

---

Type of change

• New feature (non-breaking change which adds functionality)

---

How has this been tested?

• Local test executed with UniversalProvider using the new namespace:

  const provider = await UniversalProvider.init({ projectId: "test", relayUrl: "wss://relay.walletconnect.com" });
  await provider.connect({
    namespaces: {
      solaxy: {
        methods: ["getBlockHeight", "getBalance"],
        chains: ["solaxy:1936682104"],
        rpcMap: {
          1936682104: "https://mainnet.rpc.solaxy.io",
        },
      },
    },
  });

---

Note

Add Solana/Solaxy namespace support by instantiating a Solana RPC provider and export it from providers index.

• UniversalProvider (providers/universal-provider/src/UniversalProvider.ts):
  • Extend namespace switch to handle solana and solaxy, instantiating ./providers/solana.js via dynamic import.
  • Keep existing eip155 -> Eip155Provider and default -> GenericProvider paths.
• Providers Index (providers/universal-provider/src/providers/index.ts):
  • Export SolanaProvider from ./solana.js.

^{Written by Cursor Bugbot for commit 7b009c4. This will update automatically on new commits. Configure here.}

[github-actions]

All contributors have signed the CTA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[Marcolist]

I have read the CTA Document and I hereby sign the CTA

[Marcolist]

Solaxy is a Sealevel-VM-compatible Layer-2 built on Solana.
This PR adds native support for it through the Universal Provider,
enabling WalletConnect apps to interact with Solaxy via the standard Solaxy RPC.

[Marcolist]

recheck

[ganchoradkov]

hey @Marcolist, thanks for the PR!
Looking at the subprovider, it seems all requests are piped directly at the RPC node. Shouldn't there be also handling to send requests to the wallet when needed?
Also I think even tho there is no current Solaxy sub provider, the generic one should be able to handle it exactly as in your usage example

[Marcolist]

hey @Marcolist, thanks for the PR! Looking at the subprovider, it seems all requests are piped directly at the RPC node. Shouldn't there be also handling to send requests to the wallet when needed? Also I think even tho there is no current Solaxy sub provider, the generic one should be able to handle it exactly as in your usage example

That’s a good point — Solaxy currently runs a Sealevel-compatible RPC layer, so all standard Solana methods work via the generic subprovider.
However, Solaxy uses a zk-Rollup architecture underneath, and future releases might expose additional RPC methods (e.g. proof submission or rollup state queries).
For now I’m fine reusing the Solana provider, but I’d like to keep the chain registered explicitly under solaxy:1936682104 so we can easily extend it once zk-specific RPCs go live.

[Marcolist]

Thanks for the feedback!
I’ve updated the PR to reuse the existing Solana provider for the solaxy: namespace instead of introducing a new provider file.
Solaxy’s RPC layer is fully Sealevel-compatible, so this simplifies the integration while keeping the solaxy:1936682104 namespace ready for future zk-Rollup–specific RPCs or wallet integrations.

Ready for review 👍