Improvement: Optimize and Unify Ethereum Dependencies (Remove Web3.js)
Nobody has claimed this yet.
- #95 by @Rav1Chauhan — closed without merging
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- blockchain, frontend
Research direction
Read Transaction.js, WalletContext.jsx, TransactionReview.jsx, and package.json to trace where djed-sdk uses web3.js and where viem is already used. Check whether djed-sdk supports a provider-agnostic mode, then assess the scope of replacing its used functions with viem. Done means the SDK uses viem consistently and web3 is removed from package.json; the payload names no tests to run.
Written by the indexing model from the issue text.
Description
[y] I have checked for duplicate issues
Description
The SDK currently bundles two large Ethereum libraries: web3.js (legacy v1.x) and viem (modern, lightweight).
- Transaction.js relies on djed-sdk which uses web3.js.
- WalletContext.jsx and TransactionReview.jsx use viem.
Problem
This significantly bloats the final bundle size (~300KB+ unnecessary weight) and confuses developers about which library to use for new features.
Proposed Solution
Refactor the SDK to use viem exclusively if possible.
- Check if djed-sdk has a provider-agnostic mode or if we can instantiate the Djed contracts using viem instead of web3.js.
- If djed-sdk strictly requires web3.js, wrap it or investigate migrating the few utilized djed-sdk functions to direct contract calls using viem.
- Remove web3 from package.json dependencies.
Benefits
- Massive reduction in bundle size (crucial for a widget SDK).
- Consistent API across the codebase.
- Better performance (viem is significantly faster than web3.js).
[y] I want to work on this issue
- Dominant language
- JavaScript
- Stars
- 16
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from StabilityNexus/StablePay
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
StabilityNexus/StablePay#64 · 1 comment ·
-
[BUG]: Missing SDK API documentation and incomplete developer-facing usage guide in StablePay READMEOpenbug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
StabilityNexus/StablePay#104 · 1 comment ·
-
[BUG]: `stablepay-sdk` README documents an unrelated thirdweb app instead of the actual SDK APIOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
StabilityNexus/StablePay#102 ·
-
[FEATURE]: Centralize transaction initialization and quote fetching to avoid duplicate RPC calls in the widgetMay be free again @CaptainLevi2k04 claimed this 81 days ago, and no pull request is open. Openenhancement
Difficulty 4/5 3-5 days Newbie friendliness 38/100
StabilityNexus/StablePay#101 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
StabilityNexus/StablePay#96 · 1 comment ·
All issues in StabilityNexus/StablePay
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 Under an hour Newbie friendliness 82/100
Leonxlnx/taste-skill#216 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
all-contributors/cli#690 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day