Skip to content
This repository was archived by the owner on Mar 5, 2025. It is now read-only.

Commit beae979

Browse files
tiny edit at ethers.md
1 parent 174caf8 commit beae979

File tree

2 files changed

+1
-2
lines changed

2 files changed

+1
-2
lines changed

docs/docs/guides/basics/sign_and_send_tx/wallet_of_eth_node.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -169,7 +169,6 @@ import { Web3 } from 'web3';
169169
const web3 = new Web3(/* PROVIDER*/);
170170

171171
// Second step: add an account to the Ethereum node and unlock it
172-
// IMPORTANT: never unlock an account on the mainnet. Use this only with your local dev node.
173172
const account = {
174173
privateKey: '0xb45b02f408a0dd0996aab2b55a54f4ed7735f82b133c0786a9ff372ffaaf11bd',
175174
address: '0xe4beef667408b99053dc147ed19592ada0d77f59',

docs/docs/guides/migration_from_other_libs/ethers.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ sidebar_label: 'Migration from ethers.js'
44
title: 'Migration from ethers.js'
55
---
66

7-
Follow this guide, if you're currently using the ethers.js library to interact with the Ethereum blockchain and want to migrate to web3.js.
7+
Follow this guide, if you're currently using the ethers.js library to interact with the Ethereum blockchain and want to migrate to web3.js. This guide is for ethers v5 and v6. And, if there are differences, code for both would be provided. And, if you find something missing, or worth adding, feel free to open a PR, please.
88

99
However, migrating from a library to another would usually need careful changes. But, ethers.js have lots of similarities with web3.js and migration would usually be easy and straightforward. However, you still need to check your code for possible tweaks as needed.
1010

0 commit comments

Comments
 (0)