Are the current versions of (win+mac) clients already equipped for the upcoming short/long functions with market pegged assets, or will there be an update to install to be *compliant* after the hard fork?

Hey guys, I know that all the info I am asking for will eventually be forthcoming, with future versions of the gui being more user friendly, etc., but if you have a moment I was hoping to clarify a couple other issues regarding structure/setup of the current gui wallet:

1. The first thing the gui wallet asks after I install it onto a computer is for a password (to be used to unlock the wallet). Is that password just for encryption of the wallet itself? In other words, if I dump_private_key for an account, will that private key then be unencrypted or "naked", so that when I import_private_key into the new wallet, I won't have to enter the old wallet password every time I want to access the account in the new wallet? Sorry if this sounds really basic, but I am just trying to solidify my understanding of the basic protocol drawing from my (limited) understanding of BTC qt., etc.

2. Is there a way to change the password used to encrypt/unlock the wallet?

3. Tonyk mentions "key pairs" in this post:   https://184.154.208.204/index.php?topic=7049.msg93891#msg93891
Does that just mean *Private/public* key, or is there more than one private/or/public key associated with each account?
Is there a new/additional private key created every time a transaction is made with an account?
If so, what is the process to ensure that all transactions/private keys are accounted for and properly transferred when exporting/importing an existing account into a new wallet?

Ok, I will be patient
Thanks again for your help!

I have multiple BTSX wallets I am trying to set up for family members. Can I seed fund each wallet with funds from the previous wallet?

In other words, can funds be sent from a registered address to a public key, or is there some other process that needs to be done to transfer seed funds?

I tried to seed the wallets by posting multiple public keys on the "seed funds" thread, but I was politely asked "why I needed to register again?" 

Could I get some seed/registration funds? Thanks!

BTSX6pAvEM5ZR9h7AMsRarhJJziXx4BEeyxGtt9vWRpK2Uv3bEQJHB

Also, for or future reference, can funds be sent from any registered address to a public key like the one listed above? Or is there some different procedure for sending seed funds?

Thanks!

Quote from: crypto_prometheus_81 on August 16, 2014, 06:42:46 pm

Thanks guys, I feel like I got something

If I recall something BM said a while ago that once the master key is created the wallet becomes deterministic from then on. So as long as your wallet is backed up (and you don't create any more accounts) you're good. You can take that .json backup and move it to wallets on other machines. As long as you're not a block producing delegate it shouldn't be an issue. So technically you could keep your .json on a flash drive and load it up anywhere you like. You can also create a wallet called my_wallet_whatever and open/close it manually in the client's console screen. When you execute wallet_open my_wallet_whatever you'll be taken to the passphrase opening screen.


Keep in mind the .json is your backup as long as you don't create new accounts.

I have two accounts in my wallet but only one of them is Registered

After I compiled the wallet I created an account name which included a dot(.)

and after posting the key and recieving seed funds, the name with a (.) would not register so I created a second account in the wallet (without the (.)), and registered that account name Instead

Would a flash drive with the .json work in this situation?

I appreciate the terse reply, Even though it leaves me confused...lol

A question of a different flavor:

What is *best practice* for preventing exposure of your private PTS/AGS keys to potentially malicious 3rd party DAC wallets?

Got It, U can close the thread, tks