Add receiver name to transfer operation about graphene HOT 7 CLOSED

I thought the only supported configurations were:

• Connecting a native wallet such as cli_wallet to a trusted full node running on localhost or through a secure network path
• Using a hosted wallet

If you use the first approach, you trust the full node because you control it. If you use the second approach, you trust the hosted wallet provider not to send you JS which steals your private keys. Taking away the provider's ability to lie to you about the chain state doesn't take away their ability to steal your funds if malicious / hacked. Neither of the use cases we plan to initially support are affected by this attack vector.

from graphene.

account_create and account_update owner, active
If that is setup wrong, there could be big trouble in the near or distant future...

Search generated sterilizer_operation_types for "to_account" to find more...
https://github.com/cryptonomex/graphene-ui/blob/master/dl/src/chain/serializer_operation_types.coffee

The encrypted memo could be protected by having a to name and the blockchain address used to create the shared secret. A witness would have to ensure that they match. In this case I believe the transaction should be prevented from providing a to key_id..

The account's memo_key is vulnerable too, that one looks a bit complicated..

I was just thinking about support for named assets and accounts everywhere ... but that was too much in the way of code changes. Great idea, to narrow it down like this...

from graphene.

https://bitsharestalk.org/index.php/topic,16829.msg215313.html#msg215313

from graphene.

How about "send to name" for transfer only. However, the CLI and GUI can give the option to append check digits and account ID onto the name... https://bitsharestalk.org/index.php/topic,16829.msg216606.html#msg216606

from graphene.

Yes, web wallet is convenient, but it's poor security
once the JS file been replaced, all user's private key will been stealed.
this is the only way I can think to enhance security,
place the web server in a private network, keep ssl certify file safe.

and we should have another choice to get more security light wallet.
we need desktop application, mobile app ....

from graphene.

A chrome extension would be cool as well

from graphene.

We have an assert op, I will document how to do this.

from graphene.