Giving up private keys for multiple coins to one untrusted source?
Do you even understand what i said?
Noone except you knows your private key, you are not giving them up to anyone.
If I am confused then perhaps you can help. Are you saying that you don't need to input private keys into a XUC wallet which communicates with to the internet?
How is that different from moving your BTC keys from one wallet to another
In that case we should completely abolish the whole idea of private keys from crypto altogether. If you have doubts, how about looking through the source code when it's available, else all this is is FUD.
There is a BIG difference. BTC has been around a long time and I would be moving keys between trusted wallets. However, I don't know you, your coin, your software, or your full intentions. Also, when I ask reasonable questions and you seem to get frustrated, that is a bad sign.
Basically I agree that using private keys for anything other than their original intended software is a bad idea, I mean for one thing it makes this project a lot higher of a target for keyloggers given that they now only need 1 password to access EVERY private key you have imported. It would be better if we could just sign a message using our original wallets and somehow use that as a private key that way everyone is one step removed risk wise and still able to prove ownership.
I think that only applies if you use a wallet other than the one i will provide. The risk is there for those who go outside the prescribed directions, the keys are only imported and no other copy is kept, so if your wallet is kept secure there will be no problems.
As for key loggers if a user opens themselves up to it then there is little we can do to help , it's no different a situation from right now, you could be unfortunate enough to have one on your machine already trying to get at your keys, how is that in anyway related to this project?
This is a crypto currency that will be based off Bitcoin code, securing your wallet is your job , how have you been keeping them safe all this time and how does this project change that?
Again this is just FUD since all the security issues are on the users end not the actual app itself.
As for using your suggested method, i agree that would be great IF it was possible, but we are not worried about ownership in this case. we are concerned about your balance to use to calculate your % stake.
The method you described above still requires you to have a way to redeem the coins attached to your address, which plain and simple is still your private keys.
Wait, so you are saying that after we import using our private keys we/someone can't use dumpprivkey after unlocking the wallet?
1) Your comment assumes that private keys have some other job other than proof of ownership.
2) You raise the issue of key loggers
3) You claim that this enables having password gives access to all private keys
4) You then suggest a method of proof of ownership that does nothing for Proof of % stake and has no means of redeeming said stake.
And i answer
1) The job of private keys is proof of ownership with the ability to redeem which is what I am acheiving with my method
2) Key loggers have always been around and it is your responsibility to make sure you do not install any on your computer, does BTC have any anti- keylogger code or are you asking me to make one for you?
3)Which password do you mean? if it is the login password, am i supposed to start teaching people to create secure login passwords? If it's the wallet password, am i supposed to teach people how to secure their own respective wallets? NO to both questions, it is your job as a user to secure your wallet. It is like that with every coin.....why are you looking for it to be different here?
4) Your method can prove address ownership...but do tell me HOW will someone be able to redeem? It is called a public key because it is public and available to all. Your coins are yours because you have the private key to prove it.
Funny how a lot of coins have done chain swaps and distributions in a similar manner without any of the issues you are trying to invent.
So long as the code is open source, it can be reviewed at length anytime.