0 Members and 1 Guest are viewing this topic.
I have imported keys manually (who here hasn't? the 0.9.x balances).. is it enough to back it up once after that?As mine stands now, there's a bunch of imported but unclaimed balances, and a few claimed balances.. I backed up the wallet (the .binf ile) after importing the keys.Are the funds safe this way?
1) Do not use the same wallet on two computers. - If you do this the deterministic key generation will get out of sync. This can result in missing balances and/or orders using the same key and thus difficult to cancel. We are enhancing the wallet to be able to handle this more gracefully. That said, one wallets will not be able to see the receiver of outgoing transactions sent from the other wallet. 2) Do not attempt to restore from an "old backup" - While technically the purpose of a backup is to prevent you from losing funds, the backups at this point in time are there to allow *future versions* to have a hope at recovering all of your funds. Backups are generated automatically every time you upgrade the wallet. When you upgrade only use the "most recent" backup. Generally speaking you shouldn't ever have to dive into a backup file that is older than your last transaction. While future versions may allow you to recover all of your funds, your transaction history may never quite recover all of the data you may want. 3) Do not attempt to use more than one "account" per wallet if you want to be able to easily recover from a backup - Based upon the current wallet code, if you use more than one account and attempt to recover keys it will not be able to allocate market orders back to the original account. You will be able to recover the funds/orders to one of your accounts but it may not be the same account as the original order.
Any estimation as to when we will be able to recover wallets no matter how old they are? I forgot to backup my latest wallet and now my most recent one is 2 months old and can't recover all my funds, regenerate keys doesn't work, I think its some market orders that create the problem for me.
Quote from: unsoindovo on November 18, 2014, 07:08:24 pmhi!!!windows 7 pro 64bit here..i update the wallet and all works fine...nothing lost...but i get this error logCode: [Select]getStackTrace@app.js:26:8827 ○ request@app.js:30:24118 ○ get_config@app.js:29:35629 ○ app.js:29:62715 ○ j@app.js:6:39741 ○ app.js:6:27204 ○ $eval@app.js:6:48397 ○ $digest@app.js:6:47106 ○ $apply@app.js:6:48723 ○ f@app.js:5:92484 ○ r@app.js:6:4852 ○ onreadystatechange@app.js:6:539110 assert_exception: Assert Exceptionnow >= start_timestamp: {} bitshares chain_interface.cpp:81 bts::blockchain::chain_interface::get_max_delegate_pay_per_block {} bitshares common_api_client.cpp:19 bts::rpc_stubs::common_api_client::blockchain_get_infoit is all ok???thanksThis is okay; it does not affect anything and will be fixed in the next version.
hi!!!windows 7 pro 64bit here..i update the wallet and all works fine...nothing lost...but i get this error logCode: [Select]getStackTrace@app.js:26:8827 ○ request@app.js:30:24118 ○ get_config@app.js:29:35629 ○ app.js:29:62715 ○ j@app.js:6:39741 ○ app.js:6:27204 ○ $eval@app.js:6:48397 ○ $digest@app.js:6:47106 ○ $apply@app.js:6:48723 ○ f@app.js:5:92484 ○ r@app.js:6:4852 ○ onreadystatechange@app.js:6:539110 assert_exception: Assert Exceptionnow >= start_timestamp: {} bitshares chain_interface.cpp:81 bts::blockchain::chain_interface::get_max_delegate_pay_per_block {} bitshares common_api_client.cpp:19 bts::rpc_stubs::common_api_client::blockchain_get_infoit is all ok???thanks
getStackTrace@app.js:26:8827 ○ request@app.js:30:24118 ○ get_config@app.js:29:35629 ○ app.js:29:62715 ○ j@app.js:6:39741 ○ app.js:6:27204 ○ $eval@app.js:6:48397 ○ $digest@app.js:6:47106 ○ $apply@app.js:6:48723 ○ f@app.js:5:92484 ○ r@app.js:6:4852 ○ onreadystatechange@app.js:6:539110 assert_exception: Assert Exceptionnow >= start_timestamp: {} bitshares chain_interface.cpp:81 bts::blockchain::chain_interface::get_max_delegate_pay_per_block {} bitshares common_api_client.cpp:19 bts::rpc_stubs::common_api_client::blockchain_get_info
Quote from: speedy on November 11, 2014, 01:25:12 amI think that some original posts from Bytemaster cause panic and should be edited. I was playing with the market and I was still fine restoring from an old backup.Market transactions require the wallet private key which is in the backup .. but not in the private keys of the individual accounts keys ..BM's post had the intention to make people cautious about their keys .. it's like an insurance that people not following those guidelines are considered 'advanced' users .. not regular usersGood to see your funds recovered
I think that some original posts from Bytemaster cause panic and should be edited. I was playing with the market and I was still fine restoring from an old backup.
That is really stupid question.I reinstalled my system. I thought that password from BitsharesX is the only thing that i need to restore wallet. Like in NXT.Is that right that i've lost my funds and account if i didnt export my wallet before?
What's the best practice to handle importing private keys from multiple btc/pts wallets? Is it best to create a new account for each wallet or can I import them all into one account or does it matter? I'm using version 0.4.17 BTSX wallet.
Quote from: cryptillionaire on September 15, 2014, 09:30:35 amI think we should produce a standardized document for all delegates to follow, kind of like a best practices when updating their delegate clients.Good idea .. Would you be so kind and start a new wiki page and write down your stuff? I can continue and add my stuff than Already have some scripts that make my life easier during updates
I think we should produce a standardized document for all delegates to follow, kind of like a best practices when updating their delegate clients.
Quote from: cryptillionaire on September 13, 2014, 08:43:34 pmDo you have any similar advice for users running headless delegates on servers? I run the delegate on a linux vps, but when I need to upgrade I switch to my laptop for producing blocks while recompiling on the vps (not enough RAM to recompile while running the client), so atm I have the same wallet on 2 computers. Is there a way to export the keys from one to the other so as to have a clean merged wallet? Not really a priority but it would be nice to have
Do you have any similar advice for users running headless delegates on servers?
As of 0.4.12 multiple accounts have independent deterministic key sequences so that is less of an issue.
Instead of using multiple accounts, I swap between 2 wallets on the same install. I do this by renaming APP_DATA/config.json file and APP_DATA/wallets/ folder and swap wallets in/out as I wish.Is this dangerous? seems to work for me.
Quote from: bytemaster on September 01, 2014, 07:21:19 pm3) Do not attempt to use more than one "account" per wallet if you want to be able to easily recover from a backup - Based upon the current wallet code, if you use more than one account and attempt to recover keys it will not be able to allocate market orders back to the original account. You will be able to recover the funds/orders to one of your accounts but it may not be the same account as the original order.I have 8 accounts on the same wallet Should I follow puppie's tutorial in another thread to create a wallet backup with only my main account?If I don't care what account the funds get recovered to, only that the funds are there, am I good to go with my current wallet backed up as is (with 8 accounts)?How important is this step?
3) Do not attempt to use more than one "account" per wallet if you want to be able to easily recover from a backup - Based upon the current wallet code, if you use more than one account and attempt to recover keys it will not be able to allocate market orders back to the original account. You will be able to recover the funds/orders to one of your accounts but it may not be the same account as the original order.
Quote from: cass on September 01, 2014, 09:20:32 pmok and best practise if i'm using more than one account? What can i do to backup etc... ? Or no way to do so yet?If you are using more than one account (I am) then just make sure you restore from a recent backup and that you backup regularly.
ok and best practise if i'm using more than one account? What can i do to backup etc... ? Or no way to do so yet?
But people who backed up their wallets prior to 0.4.10 should still be able to recover at some point, right?I literally had no other way of getting back on track. When installing new software kept crashing with the old data, I wiped the data folder and imported the old JSON wallet with fresh blockchain data. Heck even that was crashing for a few versions. Finally in 0.4.10 it is somewhat back on track.With the exception of a few orders probably imported from the old wallet that I can't seem to be able to cancel due to "invalid order type"(details already sent, BM is looking at it)