DNS keys to vesting BTS - what do I do?

Started by swedespade, February 08, 2015, 04:54:53 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

bench

How about reading the posts above and ask specific questions?
Be part of the change and vote for the bitshares-vision proxy!

D4vegee

Yeh i know, old topic and i aint posted for years...

I still have some old DNS wallet stuff knocking about and never claimed anything. Must be worth a bit now. Any mods have any knowledge? Remember anything?

orlander

I have a similar problem :
After claim from the genesis block, and register the name. I did not use KeyID until now...
now, I export the KeyID wallet file, and import it into BTS 0.9.2
using console command : wallet_import_keys_from_json c:\dns.json xxxx yyyy
I got a number 0
checking using vesting yyyy, I got [ ]
It look like the key did not import into BTS

Is there any other way to do it?

gnarl

This was not working for me, it produced an error "wallet is open"
Since no one has explained it simply for the non-developer crowd, here is what I tried that did not error out.

Open Keyid - login - Go to console
type wallet_export_to_json c:\keyidjsonexport

Open Bitshares - login - Go to console
type import_keys_from_json c:\keyidjsonexport Keyidpassword bitsharesusername

>> import_keys_from_json e:\jsonexport Keyidpassword bitsharesusername
10

If it actually works, a number will appear. If you run it again, the number will be 0.

In bitshares console, type rescan

After a few more hours, the keyid balances should appear when you type -  wallet_account_vesting_balances youraccountname
Then for the next 2 years you have to type -  wallet_collect_vested_balances

What a pain. Why can't they just make it vest automatically after keys are imported?

gnarl

Why is this information not sticky posted at the top of the forum?

swedespade

Working on media. A little extra goes a long way:)
BTC: 1FPc7dMfwS2j9HRDyxZxft29Ti57p5jum6
Cryptsy: 76331613e1e44f0f7e7f838c6df4c4e404150f4a

Riverhead

(wallet closed) >>> help wallet_import_keys_from_json
Usage:
wallet_import_keys_from_json <json_filename> <imported_wallet_passphrase> <account>                   Imports anything that looks like a private key from the given JSON file.
Imports anything that looks like a private key from the given JSON file.

Parameters:
  json_filename (filename, required): the full path and filename of JSON wallet to import
  imported_wallet_passphrase (passphrase, required): passphrase for encrypted keys
  account (account_name, required): Account into which to import keys.

Returns:
  uint32_t

aliases: import_keys_from_json


swedespade

wallet_import_keys_from_json <path to json wallet> <password>" was not a command

I typed help in the console but did not find any commands that were close enough to "wallet_import_keys_from_json"

I updated from keyid.info and I have  client version v0.0.5-2-gdba5398 - is there a newer version?

I'm on Windows 8.1

Thanks for your help guys!
Working on media. A little extra goes a long way:)
BTC: 1FPc7dMfwS2j9HRDyxZxft29Ti57p5jum6
Cryptsy: 76331613e1e44f0f7e7f838c6df4c4e404150f4a

vikram

Quote from: toast on February 10, 2015, 06:17:18 PM
Export wallet backup from KeyID
Go to console and do "wallet_import_keys_from_json <path to json wallet> <password>"
followed by "rescan".

Do you see your balance show up?

You need to enter an account name as well. Type "help wallet_import_keys_from_json" to see the specification for the command. And make sure you used the latest version 0.6.0 or 0.6.1.

toast

Export wallet backup from KeyID
Go to console and do "wallet_import_keys_from_json <path to json wallet> <password>"
followed by "rescan".

Do you see your balance show up?
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

swedespade

I have some DNS keys that I need to import to claim vesting BTS. What steps do I follow?
Working on media. A little extra goes a long way:)
BTC: 1FPc7dMfwS2j9HRDyxZxft29Ti57p5jum6
Cryptsy: 76331613e1e44f0f7e7f838c6df4c4e404150f4a