Loading article...
Loading article...
Stream/Area:
-
Subject:
-
Paper ID:
IJSREM69180
Volume:
10 |
11 |
Nov 2026
Pages:
1-7
Publication Frequency:
Monthly (12 issues per year)
License:International Journal of Scientific Research in Engineering and Management follows the Creative Commons Attribution 4.0 (CC BY 4.0) License, allowing free use and distribution with proper attribution.
Department of Computer Science and Engineering
Jawaharlal Nehru New College of Engineering
Department of Computer Science and Engineering
Jawaharlal Nehru New College of Engineering
Department of Computer Science and Engineering
Jawaharlal Nehru New College of Engineering
Department of Computer Science and Engineering
Jawaharlal Nehru New College of Engineering
Department of Computer Science and Engineering
Jawaharlal Nehru New College of Engineering
Crypto Wallet is a non-custodial dashboard built with Next.js and Tailwind CSS. It supports Ethereum, Polygon, BNB Smart Chain, Base, Solana and Bitcoin through one BIP39 mnemonic, using BIP32/BIP44 derivation paths for each chain. Native and ERC-20 balances are retrieved through application API routes rather than direct browser requests to RPC providers. EVM and Solana transfers are prepared and signed on the user’s device with ethers.js and @solana/web3.js; the server receives only signed transactions for broadcasting. Bitcoin support in this phase is limited to key and address derivation with bitcoinjs-lib. Mnemonics and private keys remain on the user’s device and are never sent to the server in readable form; signatures are created locally. Server-side Next.js API routes handle RPC requests, transaction history and market prices, alongside a Supabase Postgres database for caching public information and wallet backups. Before upload, the browser encrypts backups using PBKDF2-SHA256 with 210,000 iterations and AES-GCM. The passphrase is not sent to the server, so backups remain ciphertext. We tested wallet creation and import with recovery phrases and raw private keys across six chains, ERC-20 token addition, key export and network switching. The paper reports functionality, issues and improvements, including threshold signatures and Bitcoin transaction signing.
KEYWORDS
Building Crypto Wallet demonstrated that one BIP39 mnemonic can support three different signature schemes and address formats without exposing private keys to a server, provided each chain family uses the correct derivation and signing logic on the client. Testing also clarified the practical meaning of a client-side wallet. Direct browser access to chain providers exposed credentials in the client bundle or caused requests to be blocked. Moving read requests behind our own API routes addressed these problems without changing the essential custody property: the server cannot sign transactions or read private keys. This refines our original client-only objective rather than abandoning its security intent. The six objectives were fully met for four chains and mostly met for the other two; Bitcoin transaction signing remains outside the implemented scope. All five issues found in the first testing round were resolved, although the server layer introduced the limitations described in Section V-B. Future work includes threshold or multisignature approval for high-value transfers, as discussed by Goel, Bisht and Chaudhary [6], and hardware-backed key isolation based on the approaches described by Urien [2], [3]. The remaining practical improvements are encryption of the Local Storage payload at rest and implementation of UTXO-based Bitcoin transaction signing. These changes would strengthen the current proof of concept and make it more suitable for cautious day-to-day use.
[1] X. He, J. Lin, K. Li, and X. Chen, "A novel cryptocurrency wallet management scheme based on decentralized multi-constrained derangement," IEEE Access, vol. 7, pp. 185250-185263, 2019, doi: 10.1109/ACCESS.2019.2961183. [2] P. Urien, "Crypto terminal: A new open device for securing blockchain wallets," in Proc. 2020 IEEE Int. Conf. Blockchain and Cryptocurrency (ICBC), Toronto, Canada, 2020, pp. 1-3, doi: 10.1109/ICBC48266.2020.9169410. [3] P. Urien, "Wallets and crypto terminals for blockchain; introducing the Big Bang paradigm," in Proc. 2019 5th Conf. Mobile and Secure Services (MobiSecServ), 2019, pp. 1-1, doi: 10.1109/MOBISECSERV.2019.8686561. [4] S. Suratkar, M. Shirole, and S. Bhirud, "Cryptocurrency wallet: A review," in Proc. 2020 4th Int. Conf. Computer, Communication and Signal Processing (ICCCSP), Chennai, India, 2020, pp. 1-7, doi: 10.1109/ICCCSP49186.2020.9315193. [5] H. Kumar, S. Basak, S. KD, and A. H. Nalband, "Enabling secured and seamless crypto wallets: A blockchain solution," in Proc. 2023 2nd Int. Conf. Vision Towards Emerging Trends in Communication and Networking Technologies (ViTECoN), Vellore, India, 2023, pp. 1-6, doi: 10.1109/ViTECoN58111.2023.10157044. [6] A. K. Goel, V. S. Bisht, and S. Chaudhary, "Multisignature crypto wallet," in Proc. 2023 8th Int. Conf. Communication and Electronic Systems (ICCES), Coimbatore, India, 2023, pp. 476-479, doi: 10.1109/ICCES57224.2023.10192591. [7] D. He, S. Li, C. Li, S. Zhu, S. Chan, W. Min, and N. Guizani, "Security analysis of cryptocurrency wallets in Android-based applications," IEEE Network, vol. 34, no. 6, pp. 114-119, Nov./Dec. 2020, doi: 10.1109/MNET.011.2000025. [8] W. Wang and T. Van Cutsem, "I know what crypto you got last summer: A study on Web3 wallet security and privacy," in Proc. 2024 6th Conf. Blockchain Research and Applications for Innovative Networks and Services (BRAINS), 2024, doi: 10.1109/BRAINS63024.2024.10732070. [9] R. Yadav, A. Sharma, S. Kumar, and P. De, "Tracking and managing of cryptocurrency wallet," in Proc. 2024 Int. Conf. Advances in Modern Age Technologies for Health and Engineering Science (AMATHE), 2024, doi: 10.1109/AMATHE61652.2024.10582164.
Publication Date
11/19/2026
Peer Review Type
Double-Blind Peer Review
Review Rounds: 2
Documents
Article Views
0
Total views since publication
PDF Downloads
5
Total downloads since publication
Geographic Reach
5
Digital Preservation: This article is permanently archived on Zenodo and complies with all data preservation standards across major indexing platforms.
Plagiarism Screening
This manuscript has been checked for plagiarism using TurnitinPlagiarismChecker software.
Conflict of Interest
The authors declare no conflict of interest related to this research work.
Funding Information
No funding information available for this research.
Related research in the same subject area
Loading similar articles...