Hey friend I have a question. Since SAFE is open source, can’t anyone who wants to do what you offer?
1 Like
Sorry I was unclear. We can already do this right now.
5 Likes
This command lets the network create a random pub/sec key, but let’s say that I already know the Secret Key, how can I insert it so that a pubkey is generated from that. If possible this would be a great way to create brain wallets. 
3 Likes
It currently supports only providing the PK with --pk, so yeah, perhaps it can also accept a sk and derive the pk from it for creating the SafeKey.
5 Likes
But this would bypass the impossibility to use a SafeKey secret key in the --to part of safe keys transfer command (and you didn’t seem to like that).
1 Like
No, the keys create command is only to create a SafeKey, you as the owner of a sk may wanna create a SafeKey using that sk, which means you are not sharing the sk with anybody as opposed to the scenario of transferring to a sk which is what people won’t usually do, nobody shares secret keys, only public keys.
3 Likes
I just wanted to hilight that you don’t want to implement the possibility to use a SafeKey secret key in the --to part of safe keys transfer command because
nobody should give you a secret key to receive a transfer. But implementing a --sk argument in the safe keys create command is a way to indirectly allow this.
Anyway I don’t what that anymore because the new procedure don’t need it.
But there was another suggestion I made you didn’t comment: how about interpreting a missing --to argument in safe keys transfer as funding the account default SafeKey.
3 Likes
I’d personally would be very careful when it comes to transfers and the recipient not being explicit, I feel it’s safer if the user is explicitly telling where the funds/money should go rather than a default destination. E.g., the user may be confused and not exactly knowing to which account is logged in, transferring funds to it, or any other silly mistakes like those. Another option could be to have a flag which makes that more explicit rather than a default value, e.g. --to-my-wallet (or something like that).
4 Likes
I agree, but the same argument would apply for an omitted --from argument which is currently interpreted as taking funds out of account default safe key.
4 Likes
I think you are probably right. Wallet/money transfers is tricky, but this is no new, it’s the old thing about finding a balance in good UX and keeping the user safe, ATMs or banks have been facing this challenge for years now, people complain about having different PINs for the atm, purchasing, calling the bank customer care service, home banking login, etc., but at the same time they complain when they are hacked and their money is gone, so…as we move forward with safecoin and wallet UX we will have to find that balance and try to do a good job.
8 Likes