Support
Quality
Security
License
Reuse
Coming Soon for all Libraries!
Currently covering the most popular Java, JavaScript and Python libraries. See a SAMPLE HERE.
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Flexibility: The community can directly manage it to solve protocol bugs or add features.
Extension: If, for any reason in the future, a new NFT standard comes out, this wrapper can adapt to it, without needing to migrate a single byte of data.
Perpetual Storage: To avoid classic ERC721 censorship problems, NFTs made with this dApp can also be stored on-chain, always available under any circumstances.
Triple Interaction: You can use it passing through this wrapper, the DFOhub portal or the ethArt web application. They retrieve and set data from/to the same source.
No Code Snippets are available at this moment for ethArt.Refer to component home page for details.
No Code Snippets are available at this moment for ethArt.Refer to component home page for details.
QUESTION
Why Metamask if web3.js can interact directly with ganache?
Asked 2022-Mar-30 at 17:55I am new to blockchain app development, I saw a project where ganache accounts are imported into Metamask, then web3.js is used to access and print those accounts and balances on Frontend (user interface).
If web3.js can directly access ganache blockchain accounts and balances, why do we need Metamask in between?
ANSWER
Answered 2022-Feb-08 at 09:11If web3.js can directly acccess ganache blockchain accounts and balances, why we need metamask in between?
In this case, you don't need MetaMask to sign the transaction, as the node (Ganache) holds your private key.
But in a public environment (testnets and mainnet), the node doesn't hold your private key, so you'd need to sign the transaction using MetaMask (or any other tool that holds the private key).
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
No vulnerabilities reported
Explore Related Topics