Quote from: crypto_prometheus on February 09, 2015, 01:59:32 am

I had a similar issue when trying to restore a wallet from a json in the 6.0 gui:

Failed to restore wallet backup. Your original wallet has been restored. Error: invalid password (20001) Invalid Password!

The password I used was correct, I have never changed it.....

Are there instructions somewhere for restoring a wallet from a json backup using the console?

Anyone else still having this problem?

I can only access a recently saved wallet, all my other back-ups return this error (even though the passwords are correct) so I'm unable to access the majority of my BTS.

I'm experiencing the exact same problem when i try to restore an old backup.


(wallet closed) >>> wallet_backup_restore
json_filename: my_old_wallet.json
wallet_name: my_old_wallet
imported_wallet_passphrase:
Upgrading wallet...
Backing up wallet...
Wallet automatically backed up to: [edited]...version_upgrade.json
Please unlock your wallet to complete the upgrade...
wallet_name: [edited]20001 invalid_password: invalid password
Invalid password!
    {}
    th_a  wallet.cpp:1263 unlock

    {"timeout_seconds":3600}
    th_a  wallet.cpp:1285 unlock

    {"filename":"[edited]","wallet_name":"[edited]"}
    th_a  wallet.cpp:1158 create_from_json

    {}
    th_a  common_api_client.cpp:3195 wallet_backup_restore

    {"command":"wallet_backup_restore"}
    th_a  cli.cpp:626 execute_command


  keep the good work guys, your service is necessary for the entire ecosystem.

WIll the GUI support account names instead of pub keys? the QR codes will be generated based on registered bitshares account name and not pub keys right?

@jsidhu yes the wallet will support account names and QR codes will be generated based on that names (if the user has his account registered).

Hi everyone, here is a quick update to keep the community posted.

We (Pablo and I) are working hard to get our third release ready as soon as possible.
There has been a lot of changes going in the backs that are helping us to test while we develop.

Since want to give our users a clean/fast/integrated experience on the wallet, we developed and auto exchange for bitUSD/bitCNY <-> BTC
This auto exchanger will help us provide our first deposit/withdraw method inside the app.

(NOTE: We know that there are alternatives to this [shapeshift, metaexchanger and alt's gateway], and we keep an eye on them to integrate in the future)

Besides the "$15 sent to Pablo", "$12 received from Matias" type of transactions, we want the users to view something like this on the main screen.

"$250 Deposited"
"$200 Withdrawn"
"0.05 BTC sent to XXX ($11.04 USD)"


The auto exchanger works with two api calls.

Example : I want to "Deposit" 5 USD paying in BTC.

GET https://bsw-test.latincoin.com/api/v1/buy/USD_BTC/5
{
  "quote": {
    "client_pay": "0.02230252 BTC",
    "timestamp": "1423504598",
    "rate": "224.18991218",
    "client_recv": "5.00 USD"
  },
  "signature": "c495550ef134d00ec21889660772877952afc74878d3add28f2143086ae14295"
}

If you accept the quote you need to POST the quote back to the server with your desired destination address and your previously generated token.

POST https://bsw-test.latincoin.com/api/v1/accept
{
  "quote": {
    "client_pay": "0.02230252 BTC",
    "timestamp": "1423504598",
    "rate": "224.18991218",
    "client_recv": "5.00 USD"
  },
  "destination_address" : "DVS6KBKUMcWXvgY7c9sYqHv4p47baAn6NBPR",
  "signature": "c495550ef134d00ec21889660772877952afc74878d3add28f2143086ae14295",
  "token"    : "66ecd0a1f222f3edfce79615896cfc91ecb6487af0d00a6cf2ca9d41cb96d32f"
}

After that a transaction will be generated waiting for the payment to be made.

{
  "tx": {
    "status": "WP",
    "rate": "224.18991218",
    "cl_recv_curr": "USD",
    "quoted_at": "1423504598",
    "cl_recv_addr": "DVS6KBKUMcWXvgY7c9sYqHv4p47baAn6NBPR",
    "cl_recv": "5.00000000",
    "cl_pay": "0.02230252",
    "id": 126,
    "cl_pay_curr": "BTC",
    "cl_pay_addr": "BxMU8x3EU1mF2kNan4fyCwu7MhWNPAPjRY"
  }
}


The token is obtained after a signup process with the server.

GET https://bsw-test.latincoin.com/api/v1/signup
{
  "msg": "SignMePlease|c90355493833bfa8f739923f7f83d550063d0aa2d943cae8f0f88c11af771b99|1423505360|513424133231708f60bfffdeff9cf9929f35741f6318d4887929667e935d6cec",
  "signature": "1f7925047f1d26c435bd38e88c2c018c74528b229836df40f19be046649ba41884771a2cc7951f684760f654c9b824cf8018bc89092acf84937b7723ebae6a2304"
}

"signature" is the signature of "msg" from the server in order to identify the service.

Then you have to sign "msg" with your private key and POST back to the server.

POST
{"message": "SignMePlease|c90355493833bfa8f739923f7f83d550063d0aa2d943cae8f0f88c11af771b99|1423505360|513424133231708f60bfffdeff9cf9929f35741f6318d4887929667e935d6cec", "pubkey": "DVS7uY73UseX7JVGVzQwiuQ14Z82PtjtGin8AgvSfYtY1gUrFVhVx", "signature": "2013d56e7714b17799948daf7a7353821f58e3bc61d9f50c649efdb7de718d55101ece52f616495c3a1b9ebb0a22ff952daafc6833bba03214268f0a0296ec6663"}

And a token will be generated.

{"token": "66ecd0a1f222f3edfce79615896cfc91ecb6487af0d00a6cf2ca9d41cb96d32f"}

This is a raw/ugly screen flow for the third release to have a preview of what you can expect in the next version.

http://imgur.com/hUodEQv

Texts and GUI Elements are not final so don't worry about it.

Our third release will have the same "basic" UI design and for the next release
@cass will be helping us with the UI.

+1000 awesome work!

I'm stuck at block 1603649 and the client keeps saying ...

--- there are now 4 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- in sync with p2p network
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- syncing with p2p network, 68892 blocks left to fetch
--- there are now 3 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- in sync with p2p network
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- syncing with p2p network, 68961 blocks left to fetch
--- there are now 3 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 2 active connections to the p2p network

I've already removed peers db and nothing changes.


(wallet closed) >>> about
{
  "blockchain_name": "BitShares",
  "blockchain_description": "Life, Liberty, and Property for All",
  "client_version": "v0.5.3",
  "bitshares_revision": "8c908f81510e7103b41323bcf5a5731047c59994",
  "bitshares_revision_age": "10 days ago",
  "fc_revision": "64c6c01b806efcf70bb06aeb55ca317492123d80",
  "fc_revision_age": "25 days ago",
  "compile_date": "compiled on Jan 31 2015 at 04:44:06",
  "boost_version": "1.56",
  "openssl_version": "OpenSSL 1.0.1i 6 Aug 2014",
  "build": "osx 64-bit"
}

(wallet closed) >>> info
{
  "blockchain_head_block_num": 1603649,
  "blockchain_head_block_age": "8 days old",
  "blockchain_head_block_timestamp": "2015-01-24T01:18:30",
  "blockchain_average_delegate_participation": "0.14 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_share_supply": "2,498,419,725.46411 BTS",
  "blockchain_blocks_left_in_round": 29,
  "blockchain_next_round_time": "at least 5 minutes in the future",
  "blockchain_next_round_timestamp": "2015-02-01T09:49:20",
  "blockchain_random_seed": "27dac4b3b71302c47ec55bd794a6a4c8100b8f7c",
  "client_data_dir": "/Users/[edited]/Library/Application Support/BitShares",
  "client_version": "v0.5.3",
  "network_num_connections": 6,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2015-02-01T09:44:30",
  "ntp_time_error": 0.14476700000000001,
  "wallet_open": false,
  "wallet_unlocked": null,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}

any ideas?

default (unlocked) >>> wallet_transfer 100 DVS elmato elmato "" vote_all

4 parse_error_exception: Parse Error
Unexpected char '118' in "vote_all"
    {"c":118,"s":"vote_all"}
    th_a  json.cpp:433 variant_from_stream
Error parsing argument 6 of command "wallet_transfer": [{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]
    {"argument_number":6,"command":"wallet_transfer","detail":[{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]}
    th_a  cli.cpp:580 parse_argument_of_known_type

    {"parameter_index":5}
    th_a  cli.cpp:583 parse_argument_of_known_type
Error parsing argument 6 of command "wallet_transfer": [{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}},{"context":{"level":"error","file":"cli.cpp","line":580,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":6,"command":"wallet_transfer","detail":[{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]}},{"context":{"level":"warn","file":"cli.cpp","line":583,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"","data":{"parameter_index":5}}]
    {"argument_number":6,"command":"wallet_transfer","detail":[{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}},{"context":{"level":"error","file":"cli.cpp","line":580,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":6,"command":"wallet_transfer","detail":[{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]}},{"context":{"level":"warn","file":"cli.cpp","line":583,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"","data":{"parameter_index":5}}]}
    th_a  cli.cpp:397 parse_recognized_interactive_command

    {}
    th_a  cli.cpp:447 parse_recognized_interactive_command
Error parsing command "wallet_transfer": Parse Error (4)
Unexpected char '118' in "vote_all"
Error parsing argument 6 of command "wallet_transfer": [{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]

Error parsing argument 6 of command "wallet_transfer": [{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}},{"context":{"level":"error","file":"cli.cpp","line":580,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":6,"command":"wallet_transfer","detail":[{"context":{"level":"error","file":"json.cpp","line":433,"method":"variant_from_stream","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":118,"s":"vote_all"}}]}},{"context":{"level":"warn","file":"cli.cpp","line":583,"method":"parse_argument_of_known_type","hostname":"","thread_name":"th_a","timestamp":"2015-01-29T05:23:29"},"format":"","data":{"parameter_index":5}}]

No for the mid Feb release.
We plan to support it later when the mail subsystem is well tested. Anyway you will have some level of privacy choosing from which balances you want to spend and to which balance you want to receive.