You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Making use of the seed phrase and account number is a bit cumbersome, especially if you have multiple wallets. Users would rather want to make use of their wallet private key to choose a specific wallet that they want to make use of in the sell_nfts.js and cancel_on_sale_nfts.js script files.
Basic example
Instead of providing a seed phrase and wallet account number, provide a wallet private key. Metamask should load that wallet and use it for the selling functionality.
Motivation
Making use of the seed phrase and account number is a bit cumbersome and problematic when you have multiple wallets.
The text was updated successfully, but these errors were encountered:
A new walletPrivateKey field has been added to the sell_nfts.js and cancel_on_sale_nfts.js scripts. The seed phrase, password and wallet account number fields were removed.
Retrieving your wallet private key:
Setup and login to metamask
Go to your metamask
Select the wallet that you would like to make use of from the drop down of accounts.
Click on the settings (three dots)
Choose account details
Choose export private key
Enter metamask password
Copy your private key as the value for your walletPrivateKey field.
Summary
Making use of the seed phrase and account number is a bit cumbersome, especially if you have multiple wallets. Users would rather want to make use of their wallet private key to choose a specific wallet that they want to make use of in the sell_nfts.js and cancel_on_sale_nfts.js script files.
Basic example
Instead of providing a seed phrase and wallet account number, provide a wallet private key. Metamask should load that wallet and use it for the selling functionality.
Motivation
Making use of the seed phrase and account number is a bit cumbersome and problematic when you have multiple wallets.
The text was updated successfully, but these errors were encountered: