0 Members and 1 Guest are viewing this topic.
Not sure I follow entirely either - Are you using a method here similar to deterministic wallets? http://bitcoinmagazine.com/8396/deterministic-wallets-advantages-flaw/If so, is the basic overview usage . .Chain creator uses:PublicKeyB = somefunction1(PublicKeyA,chainID); Sharedrop recipient uses:PrivateKeyB = somefunction2(PrivateKeyA,chainID); We're getting some flak and caution (rightly so) for requiring private keys to claim LTS . . reconsidering alternatives.
Quote from: bytemaster on July 14, 2014, 06:15:01 pm3) Sign the new public key & chain ID with the private key belonging to the BTC/PTS address.4) Export a new wallet file that contains the new private keys + signatures from the BTC keys.So just so I understand it, does that mean that your shares in the new DAC are sent from the old BTC address which was written into the genesis block, to the new addresses that you just generated with this export feature? i.e. you are using your AGS private key to sign a transaction sending your shares to this new address?Can I try this out in the next dry run?
3) Sign the new public key & chain ID with the private key belonging to the BTC/PTS address.4) Export a new wallet file that contains the new private keys + signatures from the BTC keys.
I just added support in the blockchain necessary to create a trusted wallet migration tool that will do the following:1) Take a Chain ID + BTC Wallet/Password 2) Create a new public key for each address in the BTC wallet3) Sign the new public key & chain ID with the private key belonging to the BTC/PTS address.4) Export a new wallet file that contains the new private keys + signatures from the BTC keys.The new wallet file can then be imported into a wallet for Chain ID and used without risking the theft of your BTC/PTS keys.
Quote from: spartako on July 14, 2014, 04:53:38 pmIs it possibile using ags and pts keys as "master keys" and using new generated keys in the genesis block for each dacs?No, because we don't know the AGS and PTS public key, just the address (hash of public key). This allows us to verify signatures but not perform other useful tasks.
Is it possibile using ags and pts keys as "master keys" and using new generated keys in the genesis block for each dacs?
When will claiming genesis balances without importing private keys be supported in the toolkit?i.e. claiming by signing with private keys (proof of ownership) instead of having to trust every single DAC with your private keys.IMHO, we can't launch anything without this since once there's a trojan DAC binary and it has compromised some private keys then it could kill the whole bitshares ecosystem.