4

A beta version of metamask for mobile has been released recently. You can try it from here


2

A dApp consists of two different parts: the blockchain part and the more traditional www interface part. The blockchain part has no idea about cookies, it's deterministic and can't communicate directly with the external world. All information has to come and go through nodes. The more traditional www interface part is almost just like any other website. So ...


2

Metamask is a browser extension, so you can only use it from the browser. You can do this in the following way: Create a file web3-require.js: Web3=require('web3'); Install web3 and browserify npm install web3 npm install browserify Create a browserified version of web3: browserify web3-require.js -o web3-browserify.js Create test.html: Test ...


2

In Ethereum there is no such thing as super nodes. You can have several differ sync types like. Fast, Full and Full(archived). But they will all be able to donthe same. Also doing this in mainnet might get a bit pricey. Let me suggest you checkout test nets for Ethereum Classic like Kotti. Where you can receive test Ethereum for free through a faucet and ...


2

Metamask is not correctly estimating the gas because this is not your fallback function. A fallback function is of the format (notice there is no function name): function() external payable {} If you are not providing data to the transaction in Metamask, it will assume you are sending a normal transaction and will estimate 21000 gas. In order to correctly ...


2

I fixed it. Add this code in app.js: // MetaMask injects its own web3 instance in all pages, override it // as it might be not compatible with the one used here if (window.web3) window.web3 = web3;


1

They could possibly be one. Although in their current state they don't steal any data. (at least from my knowledge)


1

Methods of a contract can be accessed by methods method of a contract instance. And the transaction can be either called by call() method or sent by send() method. So, you should use smth like that: contractInstance.methods.notarize(item).send((e,r) => {console.log(e,r)}) See more info in the web3js documentation.


1

You can lookup 82661dc4 via the 4byte.directory: See here: https://www.4byte.directory/signatures/?bytes4_signature=0x82661dc4 web3.eth.abi is part of web3.js 1.2.x, while Metamask uses web3.js 0.2.x See this link on how to use web3.js 1.2.1 with metamask: problem connecting web3 v 1.2.1 with metamask : 'currentProvider' of undefined


1

In your case you have 2 running blockchains. The first one is developement blockchain spawned by truffle and you can access its rpc using : http://127.0.0.1:9545 as shown in your terminal and the second one is ganache's chain which you can access its RPC using http://127.0.0.1:7545 If you are deploying your contract using Truffle look at truffle.js file ...


Only top voted, non community-wiki answers of a minimum length are eligible