Add Viem v2 & Wagmi v2 packages, and remove Ethers dependency

[CedarMist]

Description

Add support for Viem v2 and Wagmi v2. Remove Ethers dependency.

Replaces https://github.com/oasisprotocol/sapphire-paratime/pull/164

Details

• Simplified sapphire-paratime dependencies

  • Removed ethers, this reduces bundled size significantly when used standalone or with Viem
  • Removed tweetnacl.js, extracted necessary functions into munacl.ts
  • Removed generic sapphire.wrap function, it now exposes wrapEthereumProvider which only wraps EIP-1193 compatible providers

• Tests:

  • Removed many mock based tests, instead relying more heavily on integration tests to verify actual functionality
  • All CI tests run through a local RPC proxy (clients/js/scripts/proxy.ts) which will die if any unencrypted transactions, calls or gas estimates are made.
  • This ensures that the clients & integrations apply encryption consistently, and will prevent any regressions where encryption is accidentally broken.

• Integrations:

  • Each SDK has its own integration package + tests
  • @oasisprotocol/sapphire-ethers-v6
  • @oasisprotocol/wagmi-v2
  • @oasisprotocol/viem-v2

• Removed duplicate example projects (e.g. where two projects use the exact same underlying libraries)

  • Each example project also serves as an integration test
  • hardhat-viem (Hardhat + Viem)
  • onchain-signer (Hardhat + Ignition + Ethers v6)
  • hardhat-boilerplate (Hardhat + Ethers v5 + frontend & bundling)
  • wagmi-v2 (Wagmi + frontend & bundling)
  • wagmi-v1

[netlify[bot]]

✅ Deploy Preview for oasisprotocol-sapphire-paratime canceled.

Name	Link
🔨 Latest commit	d956ad7de0a2bc1c1d37857a7cf17e4fa6a158f5
🔍 Latest deploy log	https://app.netlify.com/sites/oasisprotocol-sapphire-paratime/deploys/66a86876ff5f210008cbaece

[CedarMist]

Feedback from Matevz

• use @noble/curves rather than munacl.ts
• need to double check that multiple signers in hardhat with ethers work
• does walletconnect & rainbowkit etc, work on mobile?
• wagmi v2 example encrypts the deployment transaction
  • we want unencrypted deployments, always?
• pure viem-v2 example in integrations
• tag current branch as 1.x / stable
• new stuff goes as 2.x / beta?

[matevz]

* tag current branch as 1.x / stable
* new stuff goes as 2.x / beta?

Sleeping over this, I would name the stable branch as clients/js/1.3.x and keep the new refactored codebase inside the main branch. If we find anything worth fixing in the stable branch as well, then we backport the fix from main to clients/js/1.3.x. If the fix is solely for 1.3.x, then we just fix the issue on the branch directly.