-
Notifications
You must be signed in to change notification settings - Fork 67
Parity shell white window #205
Comments
ETH transactions with selecting local key and typing password works fine |
You should avoid using Parity UI/signer for this. Use |
I've got the same issue. @Tbaut Could you explain more about how to use personal_sendTransaction instead of Parity UI/signer? |
@kazushige359 you could use MyCrypto Desktop App if you're not confident with using the command line. The advice I gave above isn't meant to be the only way of doing things, and it is not user friendly at all. |
Hello, I have the same issue. I always use the Parity UI integrated in Parity version 1.x, now i'm using this shell and I'm no more able to send transfer. Thank you. |
Thank you for the comment. I didn't use Parity UI, instead unlocked my account from terminal like this. It worked for me.
|
Done, but now I have this error: |
@vm-linescode When you unlock an account Parity disables the UI. At least that's what happened in the past when the UI was part of Parity. Try |
@vn-linescode we advise to use Metamask or MyCrypto Desktop wallet on to of a Parity full node to send transactions. Parity UI is not in a state where et can be advised unfortunately. |
Sure, you have to select the JSON file in the key folder |
I'm using tons of wallets, MyCrypto seems not to fit my requirements :( EDIT: I did a little java client that uses RPC to send transactions, i'm OK with it, I hope continue to use the UI for contract creation and invokation. |
Okay thank you. So (unrelated to this ticket) can you tell me what the correct way is of allowing the Parity UI on nodes where an account is unlocked? This is a common use case for us. It is secured by SSH tunnel so no security risk. |
I don't know how Parity UI connects to Parity, I used to have 2 parity listening into 2 different ports, but I can't see any configuration on UI. |
I try to deploy my contract with truffle by steps below:
parity --config node0.toml
npm run electron
migrate --network local
with truffle config:The text was updated successfully, but these errors were encountered: