BitShares Forum
Other => Graveyard => DevShares => Topic started by: wackou on January 08, 2015, 02:13:31 pm
-
I tried importing my BTS private keys, however out of the 3 I tried, only 1 gave me some DVS (and less than expected)...
Is there a way to check allocation or the genesis block for which addresses should have some funds?
I also tried to importing some PTS keys (that donated to AGS), which did not fail, and no funds there either... Maybe I'm doing something wrong?
-
Note: I did call wallet_rescan_blockchain, just to be clear...
-
I also successfully imported my keyhotee ID (wackou), and nothing there either...
-
The next release should have a "wallet_import_keys_from_json" command that can be used.
just wait for this version, it's hard to import wallet now.
PTS and AGS no longer have devshare, have a view for this
http://bytemaster.bitshares.org/update/2015/01/08/DevShares-Reloaded/ (http://bytemaster.bitshares.org/update/2015/01/08/DevShares-Reloaded/)
-
Thanks, missed that post, had still an 80/10/10 distribution in mind, hence the reason I was expecting some to be there. To be fair, there are some PTS addresses in genesis.json, not sure what purpose they serve:
https://raw.githubusercontent.com/BitShares/bitshares/dvs/0.4.28/libraries/blockchain/genesis_bts.json
https://raw.githubusercontent.com/BitShares/bitshares/dvs/0.4.28/libraries/blockchain/genesis_dvs.json
(look for addresses that start with 'P')
I guess I'll have to wait, then, however it still felt weird that the private key import seemed to work correctly but that there was no balance associated with them...
-
Thinking about it, it does bother me that one key I imported gave me a (smaller than expected) balance (the one from my delegate wackou-delegate), while the other 2 keys did not (and all 3 keys were created roughly at the same time, and had a non-zero balance since pretty much the beginning). Do you happen to know the exact date of the bts snapshot used for devshares?
I guess I'll wait, but that's a pity, as I was hoping to get a delegate voted in as it's quite easy right now given that the init delegates have a very low number of votes :'(
-
Thanks, missed that post, had still an 80/10/10 distribution in mind, hence the reason I was expecting some to be there. To be fair, there are some PTS addresses in genesis.json, not sure what purpose they serve:
https://raw.githubusercontent.com/BitShares/bitshares/dvs/0.4.28/libraries/blockchain/genesis_bts.json
https://raw.githubusercontent.com/BitShares/bitshares/dvs/0.4.28/libraries/blockchain/genesis_dvs.json
(look for addresses that start with 'P')
I guess I'll have to wait, then, however it still felt weird that the private key import seemed to work correctly but that there was no balance associated with them...
Maybe those PTS addresses are the BTS that got sharedropped to PTS during the merger. I would assume those BTS would also be included in Devs and since they haven't been claimed, one would need to claim the associated Devs with a PTS key. Just a theory.
-
Maybe those PTS addresses are the BTS that got sharedropped to PTS during the merger.
Yes, could be. Or they could be PTS addresses from the Feb. 28th snapshot for BTS too. I keep thinking I should have some BTS associated to my PTS addresses, but I remember now that I donated them after the snapshot :-[ I guess wishing really hard for something to be true does not make it true :'( :)
-
There have a way to import private key, but it's stupid.
wallet_account_list_public_keys account_name from bts client, and it list all the address on you account.
take each native_address and check on https://raw.githubusercontent.com/BitShares/bitshares/dvs/0.4.28/libraries/blockchain/genesis_dvs.json (https://raw.githubusercontent.com/BitShares/bitshares/dvs/0.4.28/libraries/blockchain/genesis_dvs.json).
If any address have balance then dump private key from bts client and import to dev client.
wallet_dump_private_key native_address
Any better way?
-
Maybe those PTS addresses are the BTS that got sharedropped to PTS during the merger.
Yes, could be. Or they could be PTS addresses from the Feb. 28th snapshot for BTS too. I keep thinking I should have some BTS associated to my PTS addresses, but I remember now that I donated them after the snapshot :-[ I guess wishing really hard for something to be true does not make it true :'( :)
Yes those PTS addresses in the initial_balances section are from BTS genesis that haven't been claimed yet. The ones in vesting_balances section are from VOTE/DNS sharedrop.
Are you sure the private key you are importing is correct account key to access TITAN deposits, or actually controls a single balance with expected funds?
In any case, next release will have wallet_import_keys_from_json command so you can import all keys from your BTS wallet.
-
There have a way to import private key, but it's stupid.
wallet_account_list_public_keys account_name from bts client, and it list all the address on you account.
take each native_address and check on https://raw.githubusercontent.com/BitShares/bitshares/dvs/0.4.28/libraries/blockchain/genesis_dvs.json (https://raw.githubusercontent.com/BitShares/bitshares/dvs/0.4.28/libraries/blockchain/genesis_dvs.json).
If any address have balance then dump private key from bts client and import to dev client.
wallet_dump_private_key native_address
Any better way?
wallet_import_keys_from_json for the normal backup / export wallet
-
Are you sure the private key you are importing is correct account key to access TITAN deposits, or actually controls a single balance with expected funds?
I did export the keys from the bts wallet using "wallet_dump_private_key account_name" where account_name is a TITAN account. I did then import them, called also wallet_regenerate_keys, but to no avail... By looking at the keys using "wallet_account_list_public_keys" as suggested by cgafeng, they do appear though in the genesis file and by importing those one by one my balance does appear. So I'll just wait for the "wallet_import_keys_from_json" command, then. (just to make sure, it's not in 0.5.0, right?)
-
I have used the menu for importing my BTS key (json file) to Devshares and it was successful.
-
ok, so I did "wallet_import_keys_from_json" in 0.5.0, and it looks like it imported everything. Thanks all for the help/comments, you guys rock +5%
-
I'm also having some trouble.
I was able to import my BTS using the import_from_json
However, I also had some BTS via the november sharedrop,
in genesis_dvs.json I have
Initial_balances:
2x BTS addresses (imported fine via import_from_json)
ShareDrop:
1 PTS address 3 times,
The same PTS address was used for an AGS contribution as well as holding some PTS
(I was able to import some via the import_private_key, but I can't match up the DVS amount int he client to any of the amounts listed in genesis_dvs.json
1 BTC address which was used for AGS donation. I can't get this one to import.
i
I've tried it several times on different accounts. I've tried the collect_vested and collect_genesis etc
Is there a way to query a PTS or BTC address to see if it's been claimed or not? I have no idea what's been imported successfully from the sharedrop....
-
There have a way to import private key, but it's stupid.
wallet_account_list_public_keys account_name from bts client, and it list all the address on you account.
take each native_address and check on https://raw.githubusercontent.com/BitShares/bitshares/dvs/0.4.28/libraries/blockchain/genesis_dvs.json (https://raw.githubusercontent.com/BitShares/bitshares/dvs/0.4.28/libraries/blockchain/genesis_dvs.json).
If any address have balance then dump private key from bts client and import to dev client.
wallet_dump_private_key native_address
Any better way?
Thanks! This worked for me. I should expect 1:1 for DVS:BTS correct?
-
I received 1:1 DVS:BTS
(unclaimed BTS) via AGS and PTS november snapshot, I have no idea... I can't correlate the amounts in the json file to amounts received. Anyone know the expected correlation for those?
Update: after carefully reviewing all the files I found a missing key in my calculations. All the PTS, BTC, and BTS are accounted for in the import.
-
There have a way to import private key, but it's stupid.
wallet_account_list_public_keys account_name from bts client, and it list all the address on you account.
take each native_address and check on https://raw.githubusercontent.com/BitShares/bitshares/dvs/0.4.28/libraries/blockchain/genesis_dvs.json (https://raw.githubusercontent.com/BitShares/bitshares/dvs/0.4.28/libraries/blockchain/genesis_dvs.json).
If any address have balance then dump private key from bts client and import to dev client.
wallet_dump_private_key native_address
Any better way?
wallet_import_keys_from_json for the normal backup / export wallet
I have made that and a window appeared that informed me that the keys successfully where imported...
But I see no accounts no funds.... nothing has changed! Any suggestion?
PS I would appreciate if somebody sent me some funds to DVS6tSjwFfYHyhpumfB6RajFKPCt1DxR8Ay2DzBY9h8RwKgrTpDhe so I can start testing the network ;)
-
There have a way to import private key, but it's stupid.
wallet_account_list_public_keys account_name from bts client, and it list all the address on you account.
take each native_address and check on https://raw.githubusercontent.com/BitShares/bitshares/dvs/0.4.28/libraries/blockchain/genesis_dvs.json (https://raw.githubusercontent.com/BitShares/bitshares/dvs/0.4.28/libraries/blockchain/genesis_dvs.json).
If any address have balance then dump private key from bts client and import to dev client.
wallet_dump_private_key native_address
Any better way?
wallet_import_keys_from_json for the normal backup / export wallet
I have made that and a window appeared that informed me that the keys successfully where imported...
But I see no accounts no funds.... nothing has changed! Any suggestion?
PS I would appreciate if somebody sent me some funds to DVS6tSjwFfYHyhpumfB6RajFKPCt1DxR8Ay2DzBY9h8RwKgrTpDhe so I can start testing the network ;)
Sent some DVS to you.
-
Sent some DVS to you.
thank you ;)