Author Topic: missing open orders from old wallet  (Read 4015 times)

0 Members and 1 Guest are viewing this topic.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
how many more?
i regenerated 10500, then 11000, 12000, 22000
is there any more?
It depends on how many transactions you've made in 0.x wallet, and what's the biggest number you've ever regenerated keys with. Say, if you've ever tried regenerate_keys with 50000 before, and made transaction(s) after that, you should try with a bigger number.
BitShares committee member: abit
BitShares witness: in.abit

Offline lcs

  • Jr. Member
  • **
  • Posts: 25
    • View Profile
how many more?
i regenerated 10500, then 11000, 12000, 22000
is there any more?

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
The rescan can only discover your funds if you have synced the blockchain fully!!

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
so i did rescan 100%
no funds to claim on BTS 2.0
what next?
Can you see all of your orders and/or balances in 0.9.3c?
If yes, you should be able to export from this wallet and import to 2.0.
If no, you may need to regenerate more keys and rescan.
BitShares committee member: abit
BitShares witness: in.abit

Offline lcs

  • Jr. Member
  • **
  • Posts: 25
    • View Profile
i quess i need to make another key, right?

Offline lcs

  • Jr. Member
  • **
  • Posts: 25
    • View Profile
so i did rescan 100%
no funds to claim on BTS 2.0
what next?

Offline lcs

  • Jr. Member
  • **
  • Posts: 25
    • View Profile
now, that was helpful, appreciate so much, cheers mate

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
As long as you are not connected to the network you do not download any blocks:
  "blockchain_head_block_num": 0,
as long as you don't have any blocks, you can't actually "rescan" the blockchain (since there is none)

I repeat: please make sure you have no firewall setup that prevents the client from connecting and let the client run for QUITE SOME TIME!!!
@xeroc I think that '176.9.234.166:13750' node is not alive, since it's not responding at this port. Maybe something wrong there. //Edit: the correct port of this node is listed below.

@lcs Here is a list of nodes which my old wallet is connected to, you can have a try:
114.92.254.159:1776
46.226.13.125:1776
176.9.234.166:1776
178.62.88.151:52249
209.126.75.85:1776

You will see something like this while syncing to the network:
Code: [Select]
--- there are now 21 active connections to the p2p network
--- syncing with p2p network, 1457307 blocks left to fetch
--- in sync with p2p network

When you see this with "info" command, you're in sync.
Code: [Select]
info
{
  "blockchain_head_block_num": 3832292,
...
}
« Last Edit: October 30, 2015, 05:14:57 pm by abit »
BitShares committee member: abit
BitShares witness: in.abit

Offline wmbutler

  • Full Member
  • ***
  • Posts: 129
    • View Profile
    • Music City Bitcoins
  • GitHub: wmbutler
Man, I feel his pain. I had endless unpredictable issues with both the old Windows and OSX client. I feel lucky that I had a version saved with all of my transactions.
PTS: PnBVP1iLTsV6U8z4BeJYhF8jMpkLhtTi9r
BTS2.0: billbutler
There are 10 kinds of people. Those who understand binary and those who do not.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
As long as you are not connected to the network you do not download any blocks:
  "blockchain_head_block_num": 0,
as long as you don't have any blocks, you can't actually "rescan" the blockchain (since there is none)

I repeat: please make sure you have no firewall setup that prevents the client from connecting and let the client run for QUITE SOME TIME!!!

Offline lcs

  • Jr. Member
  • **
  • Posts: 25
    • View Profile
Hei, xeroc
i managed to rescan, but there are no funds appearing on 2.0 anyway
what now?
thanks





it should use some memory in process, it doesnt at all
just made everything u said

Loading blockchain from: C:\Users\tredd\AppData\Roaming\BitShares\chain
Loading config from file: C:\Users\tredd\AppData\Roaming\BitShares\config.json
Initializing state from built-in genesis file
Please be patient, this will take several minutes...
Successfully replayed 0 blocks in 1 seconds.
Blockchain size changed from 0MiB to 0MiB.
Not starting RPC server, use --server to enable the RPC interface
(wallet closed) >>> open default
OK
default (locked) >>> unlock 999999
passphrase:
OK
default (unlocked) >>> rescan
OK
default (unlocked) >>> info
{
  "blockchain_head_block_num": 0,
  "blockchain_head_block_age": null,
  "blockchain_head_block_timestamp": null,
  "blockchain_head_block_id": null,
  "blockchain_average_delegate_participation": "0.00 %",
  "blockchain_share_supply": "2,499,002,518.57146 BTS",
  "blockchain_blocks_left_in_round": 101,
  "blockchain_next_round_time": null,
  "blockchain_next_round_timestamp": null,
  "blockchain_random_seed": "0000000000000000000000000000000000000000",
  "client_data_dir": "C:/Users/tredd/AppData/Roaming/BitShares",
  "client_version": "0.9.3c",
  "network_num_connections": 0,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2015-10-29T22:20:00",
  "ntp_time_error": "5.340835000000",
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "12 days in the future",
  "wallet_unlocked_until_timestamp": "2015-11-10T12:06:19",
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": false,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}
default (unlocked) >>> network_add_node 176.9.234.166:13750
OK
default (unlocked) >>> rescan
OK
default (unlocked) >>>
« Last Edit: October 31, 2015, 01:34:01 pm by lcs »

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
- stop the client
- remove everything in C:\Users\tredd\AppData\Roaming\BitShares   ... EXCEPT the wallets folder
- start the client over again


please make sure you do NOT run any firewall software that prevents your client from connecting to the internet .. that includes windows firewall!!!

Offline lcs

  • Jr. Member
  • **
  • Posts: 25
    • View Profile
hopeless, nothing happens at all, you sure i can run on that node?

Offline lcs

  • Jr. Member
  • **
  • Posts: 25
    • View Profile
it is still at, 0
and i can see it does not use anything in processes
dead

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
yes you are doing it right .. thing is you need let it run for some time to get some connections .. (the wallet will find them automatically) ...
it will take (I don't want to lie here) A LOT of time to synchronize the whole blockchain ..

depending on your hardware it will take several HOURS .. let it run over the night  ...
make sure you do not have a firewall running ..
check "info" in 30 minutes and make sure you have "network_num_connections" > 0

Offline lcs

  • Jr. Member
  • **
  • Posts: 25
    • View Profile
am i doin right?

Loading blockchain from: C:\Users\tredd\AppData\Roaming\BitShares\chain
Loading config from file: C:\Users\tredd\AppData\Roaming\BitShares\config.json
Not starting RPC server, use --server to enable the RPC interface
(wallet closed) >>> network_add_node 176.9.234.166:13750
OK
(wallet closed) >>> open default
OK
default (locked) >>> unlock 999999
passphrase:
OK
default (unlocked) >>> network_add_node 176.9.234.166:13750
OK
default (unlocked) >>> rescan
OK
default (unlocked) >>> get info
Error: invalid command "get"
default (unlocked) >>> info
{
  "blockchain_head_block_num": 0,
  "blockchain_head_block_age": null,
  "blockchain_head_block_timestamp": null,
  "blockchain_head_block_id": null,
  "blockchain_average_delegate_participation": "0.00 %",
  "blockchain_share_supply": "2,499,002,518.57146 BTS",
  "blockchain_blocks_left_in_round": 101,
  "blockchain_next_round_time": null,
  "blockchain_next_round_timestamp": null,
  "blockchain_random_seed": "0000000000000000000000000000000000000000",
  "client_data_dir": "C:/Users/tredd/AppData/Roaming/BitShares",
  "client_version": "0.9.3c",
  "network_num_connections": 0,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2015-10-29T19:16:15",
  "ntp_time_error": "5.136883000000",
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "12 days in the future",
  "wallet_unlocked_until_timestamp": "2015-11-10T08:59:35",
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": false,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}
default (unlocked) >>>

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
It should have been (missed the port number)
Code: [Select]
network_add_node 176.9.234.166:13750
That node is definitely online and available with the lastest blockchain ..

give the wallet some time to get connected

Offline lcs

  • Jr. Member
  • **
  • Posts: 25
    • View Profile
but bts 1 is not connecting

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Code: [Select]
network_add_node 176.9.234.166
rescan

wait until you see "rescan finished" or something like that

Offline lcs

  • Jr. Member
  • **
  • Posts: 25
    • View Profile
they been missing from 0.9.2 already
i regenerated, 10500, 11000, 12000, and 21000 four times
and then , now again bts 0.9.3c not connected , so how do i do it?

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
First, calm down. The keys are deterministic and can be recovered ...
You must realize that as long as you don't see your funds in BitShares 0.9.3c, you can't import them into BTS2 .. so the priority for you must be to recover your orders in BTS1.
To do so we usually only need to regenerate some keys .. as you did this already, it seems you need to regenerate MORE keys ..
then .. most importantly .. you need to wait for the client to finish rescanning the WHOLE blockchain for your market orders .. depending on how many keys your regenerate, this may take a LONG time ..

Offline lcs

  • Jr. Member
  • **
  • Posts: 25
    • View Profile
hi
nearly all my assets was on open orders
they missed from the wallet 0.9.2
i downloded 0.9.3c regenerated keys they did not appear anyway,
moderator said no need to worry they somewhere on the blockchain,
however i transfered to 2.0 i got some of my funds which wasnt on open orders, but those on open orders are gone
nearly all assets gone

anybody can help, please