Quote from: romerun on August 04, 2014, 10:59:36 AM

Quote from: ranlo on August 04, 2014, 05:09:56 AM

And just to be sure, if I import the private key associated with the shares I have, and have it swept to a new address on Counterparty, those shares will also change ownership over to the new address? Or how does that part work?

Right, they will be moved to the new address, but you can always click the "Show Private Key" of the address to back up.

Quote from: baddw on August 04, 2014, 04:35:57 PM

Quote from: ranlo on August 04, 2014, 05:09:56 AM

Thanks for the confirmation -- I was afraid of that. With the things that have happened in the past with exchanges and such, I've become extremely wary of putting funds on a site where they could potentially get access to the address. Is there anything in place to keep this from happening with Counterparty?

My understanding of the way that Counterwallet works is that the information is never really stored "on the site". The wallet is generated on-the-fly when you input the 12-word passcode.

Question for Counterparty devs: Is the passcode sent to the server(s) or is it all kept in the user's browser and run through client-side scripting? If someone compromised the webserver, is there any chance that they could see the passcode "in the clear" in the logs, or as _POST or _GET variables within the webserver software itself?

Quote

And just to be sure, if I import the private key associated with the shares I have, and have it swept to a new address on Counterparty, those shares will also change ownership over to the new address? Or how does that part work?

Yes, the shares will be transferred to the new address which is generated as part of the deterministic wallet.

Thanks for that, guys! So basically we can:

1) Sweep the address to Counterparty
2) Take the private key from Counterparty (the address that was swept to)
3) Import that key to BitcoinQT, MultiBit, etc. and use as normal again, while still using Counterparty for the shares