New answers tagged

0

Maybe use Metamask because as of March 2019 Mist(Ethereum wallet) has been deprecated. So it is natural that while using it you might run into problems. Metamask can be added as an extension in your browser and you can use Remix along with it. Using Metamask you can connect to your local or public blockchain. And use it to interact with the smart contracts ...


0

In your case, just have a simple test contract to send a small amount of ether or tokens sent from the transfer function of the original contract. Then check the balance of where it was supposed to be sent, still zero? That means it's a fraud.


1

The following Ethereum web wallets are now seeing increasing use alongside Metamask for various dapps, none of which require installing a chrome extension. Portis Fortmatic Torus Democracy <-- the last one is my project For a comparison of why you might use one wallet over another, and general design considerations that go into making a web wallet, I'...


0

When you are using the --stdio-ui parameter, you have to interact in json format. For example to reply with your password phrase use: {"jsonrpc":"2.0","id":1,"result":{"text": "password phrase"}} When experimenting it is easier to start without the --stdio-ui parameter, then you can just paste the password and enter anwers like "y".


0

Our particular constraints: using addresses as identification minimal UX trade-off The solution: A contract that generates receiver contracts The receiver address producing contract: contract Factory { address public owner; mapping ( uint256 => address ) public receiversMap; uint256 public receiverCount = 0; constructor() public { /* ...


0

I assume you can't identify the token transferrers just based on the sending address - otherwise this would be trivial (just follow the Transfer events). I personally don't quite understand why meta transactions aren't a big thing already. They enable all sorts of scenarios especially in easy user on-boarding. Sure, they have some issues and are a bit ...


1

You can run your own Geth or Parity node. Both support JSON-RPC and work on a Linux VPS (with a decently fast SSD), and use a CLI to send transactions. Parity runs a JSON-RPC server by default, and for Geth you can run it with the --rpc option. Keep in mind that if you enable JSON-RPC and use Geth or Parity to manage your private keys, the JSON-RPC interface ...


0

Well it's a decentralized world. There is no "official" way of doing things. It's also probably quite difficult to know what format "most" wallets support (if any). I was reading through the EIP67 and it's not obvious whether the value should be in Ethers or Weis. A comment here suggests weis: https://github.com/ethereum/EIPs/issues/67#issuecomment-...


0

I couldn't find any decent official specification, but Coinbase generates QR code in such format: ethereum:0xaaaaaaaaaaaaaaaaaaaaaa?value=500000000000000 where value is in Wei and not ETH (1 ETH = 1,000,000,000,000,000,000 Wei).


Top 50 recent answers are included