#ethereum #crypto #wasm #web3 #walletconnect

ethers-web

WASM library for web injected and walletconnect dApp connections

5 releases

new 0.2.0 Jun 21, 2024
0.1.3 Jun 3, 2024
0.1.2 Apr 23, 2024
0.1.1 Apr 15, 2024
0.1.0 Apr 12, 2024

#1816 in Magic Beans

Download history 113/week @ 2024-04-08 266/week @ 2024-04-15 251/week @ 2024-04-22 2/week @ 2024-04-29 45/week @ 2024-05-06 29/week @ 2024-05-13 47/week @ 2024-05-20 13/week @ 2024-05-27 188/week @ 2024-06-03 16/week @ 2024-06-10

264 downloads per month

MIT/Apache

66KB
1.5K SLoC

Quickstart

Add this to your Cargo.toml:

[dependencies]
ethers-web = "0.2"

Depending on the web framework you are using you might want to enable proper feature.

For yew you should simply enable its feature first:

[dependencies]
ethers-web = { version = "0.2", features = [ "yew" ] }

In examples folder you will find an example yew application that is using an yew::UseEthereum that will allow you to connect to chosen wallet and maintain its life cycle by fetching messages from the message loop using next() function.

The library does not deliver own message loop bacause of the limitations that yew and leptos are inside their WASM lifecycle.

There are two wallet standards implemented inside ethers-web.

EIP 1193

Eip1193 is an embedded wallet standard such as Metamask. To connect to it you just need to call connect() method and attach connected context provider as any other provider in ethers calls.

WalletConnect

WalletConnect requires a bit more setup than just making a connection. You will need PROJECT_ID and additional RPC_URL that will be handling generic rpc calls that wallet might not support.

Examples

Simply check examples folder to find example implementations you can use in your app.

Documentation

In progress of creation. For now check examples folder for implementation details for both leptos and yew frameworks

Features

  • EIP1193 injected wallet implementation
  • WalletConnect
  • Proper Leptos support
  • Documentation

Note on WASM

This library currently needs WASM to work. There is a plan to support server-side implementations, though. For now, we focus on building robust solution for WASM implementations of websites.

Dependencies

~47–66MB
~1M SLoC