BitShares Forum
Main => General Discussion => Topic started by: hazard on December 30, 2014, 06:35:49 pm
-
I tried importing my protoshares wallet from before the february cut off, but my BTS balance still shows 0.
Any ideas? What should I try next?
-
I am in the same situation.
Help is kindly appreciated!
-
did you use the latest version of bitshares(0.4.27.2)? was your bitshares wallet fully synched? did you successfully imported your wallet?(any error messages?) was your protoshares wallet encrypted in a safe pc?
-
Seems like I did not have the latest update yet. I still had 0.4.24.2.
Why did the tab 'check for updates' in the client gave me the message that no updates were available?
The blockchain is reindexing as I am speaking.
I will keep you guys updated if updating solved the problem.
Thanks
-
Update:
0.4.27.2 running, wallet fully synched, no error messages while importing PTS wallet key (message : import successful).
The balance keeps showing 0.5 bts after successful registering???
The wallet path was correct because I was able to import the same file yesterday in the new DPOS PTS client.
What might be the problem?
Thanks!
-
Instead of what you're trying to do, can you tell us what you're trying to accomplish? (XYproblem)
Are you trying to get your PTS-AGS balance into an account in Bitshares, or did you actually have PTS at the time of the snapshot and are you looking for a PTS-BTS snapshot balance?
-
I bought some protoshares early February in 2014. I have the wallet.dat file from then.
I had PTS at the time of the snapshot and am looking for a PTS-BTS snapshot balance.
How would I go about doing that?
-
Importing the wallet.dat file into the Bitshares client will do it, but before we do that, can you provide a public address that exists in your protoshares wallet, that also holds a balance as of before the PTS-AGS snapshot?
We can easily look at the genesis block and find it, plus it's allocated balance if it exists.
-
Hi
My goal is to get the BTS (from the merger of the projects DNS/VOTE that I was really interested in) I am entitled to having PTS in my wallet during the time of the snapshot.
My wallet address was PciTVvFQT52mzpmhXWd2mjh27dtmURTejJ. I had over 500 PTS at that time.
How can I get the balance to be correct in BTS?
Thanks!
-
Yep. I can see your address on the genesis.json file.
Can you describe the steps you took to import your protoshares wallet.dat file?
Take a look at:
http://wiki.bitshares.org/index.php/BitShares/Howto#Attempting_a_wallet_import_to_receive_BTSX_from_February_28th_snapshot (http://wiki.bitshares.org/index.php/BitShares/Howto#Attempting_a_wallet_import_to_receive_BTSX_from_February_28th_snapshot)
See if you're doing it as described.
(Wallet type should be Bitcoin, even though its PTS)
-
Hi
My goal is to get the BTS (from the merger of the projects DNS/VOTE that I was really interested in) I am entitled to having PTS in my wallet during the time of the snapshot.
My wallet address was PciTVvFQT52mzpmhXWd2mjh27dtmURTejJ. I had over 500 PTS at that time.
How can I get the balance to be correct in BTS?
Thanks!
afaik we can't do that yet, we must wait for the next release/version of bitshares. You can try wallet_check_sharedrop to check your sharedrop from what is already imported in your bitshares wallet. In any case keep some backups of your bts wallet in a safe place.
-
But he has protoshares from the first snapshot, that means he should have his bitshares balance.
-
Importing the wallet.dat file into the Bitshares client will do it, but before we do that, can you provide a public address that exists in your protoshares wallet, that also holds a balance as of before the PTS-AGS snapshot?
We can easily look at the genesis block and find it, plus it's allocated balance if it exists.
PrcfE7Rdu9RyZaAYaquC6uoz3moFdJFV9Z
I had about 92.5 PTS.
-
Also, I see non-zero balances with wallet_check_sharedrop, summing to 1242785229. How can I find out how many BTS I'm entitled to?
-
hazard, are you only "trying to find out" or are you actually trying to get your balance to show up on your client?
Finding out is easy.
Get all your pre-snapshot balances from all addresses you own.
Multiply by that by 644.
That's how many you're entitled to by owning PTS.
-
I'd like to sell some.
-
Yep. I can see your address on the genesis.json file.
Can you describe the steps you took to import your protoshares wallet.dat file?
Take a look at:
http://wiki.bitshares.org/index.php/BitShares/Howto#Attempting_a_wallet_import_to_receive_BTSX_from_February_28th_snapshot (http://wiki.bitshares.org/index.php/BitShares/Howto#Attempting_a_wallet_import_to_receive_BTSX_from_February_28th_snapshot)
See if you're doing it as described.
(Wallet type should be Bitcoin, even though its PTS)
Thank you for your help.
So I am entitled to (644 x amount of PTS I had on the moment of the snapshot) BTS?
The steps as I did them:
Update to the latest client, register a new account, then highlight the account, tab import keys from wallet, Bitcoin/PTS wallet type, then entered the wallet password.
I received the notification the operation was done successfully. However, my balance still shows 0.5 BTS (after registering 1-0.5 BTS)
What might be the problem?
-
Run from console :
wallet_account_list_public_keys {your_account_name}Look for the addresses from your PTS wallet in the "pts_compressed_address" sections of the text.
Can you find them?
-
I encountered the same issue. I have some PTS in my BitShare-PTS wallet long long ago. I have installed Bitshares v0.4.27.1, and try to import BitShare-PTS wallet.
This is my transaction information:
GENESIS -> BTS5gLc1wFcBx7ZA1fau31mxCmKDTtq6cpcK3vW9XdWDJ1bzW3PFu
claim PYgpUhLjTgfEsVaW2N5oR9Gbgn9JxTai3r
9,042.56427 BTS
0.00 BTS 2014/7/19 GMT+8 11:18:40AM
Why my balance is 0?
My public key is BTS7Vpyxo2o7CorEcCd4K376ibuczKvyKwUPBumscsLeje38Zd3eL
-
Run from console :
wallet_account_list_public_keys {your_account_name}Look for the addresses from your PTS wallet in the "pts_compressed_address" sections of the text.
Can you find them?
Yes, then what?
-
Can you (both) try issuing a rescan?
From the console:
rescan
-
The balance is still 0 after a rescan. However, I noticed the following error notification:
signature is not canonical
getStackTrace@app.js:27:17454
○ request@app.js:32:25344
○ app.js:30:60480
○ 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:5391
10 assert_exception: Assert Exception
!(c.data[1] & 0x80): signature is not canonical
{}
bitshares elliptic.cpp:496 fc::ecc::public_key::public_key
{}
bitshares common_api_client.cpp:2323 bts::rpc_stubs::common_api_client::blockchain_get_block_signee
{}
bitshares common_api_client.cpp:240 bts::rpc_stubs::common_api_client::batch
What's the problem with it?
-
The balance is still 0 after a rescan. However, I noticed the following error notification:
signature is not canonical
You are either using an old client version, or you are on an old fork of the chain. Upgrade your client and re-sync.
-
The balance is still 0 after a rescan. However, I noticed the following error notification:
signature is not canonical
You are either using an old client version, or you are on an old fork of the chain. Upgrade your client and re-sync.
Yep. ^^
After upgrading, re-sync by running the software with the
--resync-blockchainFlag.
-
The balance is still 0 after a rescan. However, I noticed the following error notification:
signature is not canonical
You are either using an old client version, or you are on an old fork of the chain. Upgrade your client and re-sync.
Yep. ^^
After upgrading, re-sync by running the software with the
--resync-blockchainFlag.
Hi
I am using an OSX client.
There is no possibility to run the software with other commands?
When I enter the command that you mentioned , I get the following error message:
>> --resync-blockchain
Error: invalid command "--resync-blockchain"
I have the latest version, blocks are synched.
I am getting really desperate here…
-
The balance is still 0 after a rescan. However, I noticed the following error notification:
signature is not canonical
You are either using an old client version, or you are on an old fork of the chain. Upgrade your client and re-sync.
Yep. ^^
After upgrading, re-sync by running the software with the
--resync-blockchainFlag.
My BitShares client version is 0.4.27.1. I have just downloaded the Bitshares client few days ago and when checkUpdate, it says no new update.
I have also tried the command and it says invalid:
>> resync-blockchain
Error: invalid command "resync-blockchain"
>> --resync-blockchain
Error: invalid command "--resync-blockchain"
-
--resync-blockchain is a flag.
It's used as an option when calling the Bitshares executable.
For example, on linux:
./bitshares_client --resync-blockchain
Also, 0.4.27.1 is not the latest release:
https://github.com/BitShares/bitshares/releases (https://github.com/BitShares/bitshares/releases)
-
--resync-blockchain is a flag.
It's used as an option when calling the Bitshares executable.
For example, on linux:
./bitshares_client --resync-blockchain
Also, 0.4.27.1 is not the latest release:
https://github.com/BitShares/bitshares/releases (https://github.com/BitShares/bitshares/releases)
downloaded the latest client, blocks synced, imported keys successfully
still balance 0
:(
-
@ arubi
thank you for your time!
hopefully we find the solution
there is nothing we want but becoming part of the BTS community
Somewhat disappointed that no other community members are helping newbies….
-
I have been following this thread for a few days and going through all the steps. I am also having the same issue.
-
@ arubi
thank you for your time!
hopefully we find the solution
there is nothing we want but becoming part of the BTS community
Somewhat disappointed that no other community members are helping newbies….
Can you share what is your solution?
-
--resync-blockchain is a flag.
It's used as an option when calling the Bitshares executable.
For example, on linux:
./bitshares_client --resync-blockchain
Also, 0.4.27.1 is not the latest release:
https://github.com/BitShares/bitshares/releases (https://github.com/BitShares/bitshares/releases)
I have read the release note of 0.4.27.2 and it said there is no hot fix except some GUI changes.
I am using windows, so after I manually type the command you instructed, I was stuck there, have no idea what to do.
-
@ arubi
thank you for your time!
hopefully we find the solution
there is nothing we want but becoming part of the BTS community
Somewhat disappointed that no other community members are helping newbies….
Can you share what is your solution?
Hi
I still haven't found a solution myself.
Maybe we should start another thread in the forum?
-
Sorry guys, between work and finals at uni. I just can't find the time to log into the forum and reply.
If you can't run --blockchain-resync , then you'll have to manually delete the blockchain and re-download.
On windows the blocks are found at:
C:\Users\UserName\AppData\Roaming\BitShares\
(change Username to your own username)
Delete the folders:
And re-launch.
DO NOT DELETE THE wallets FOLDER
-
I'm starting to think this is a bug introduced in some recent update.
-
Sorry guys, between work and finals at uni. I just can't find the time to log into the forum and reply.
If you can't run --blockchain-resync , then you'll have to manually delete the blockchain and re-download.
On windows the blocks are found at:
C:\Users\UserName\AppData\Roaming\BitShares\
(change Username to your own username)
Delete the folders:
And re-launch.
DO NOT DELETE THE wallets FOLDER
Hi
No problem for the delay :-)
I am running the OSX version so I can't manually delete and re-download the blockchain?
-
I'm starting to think this is a bug introduced in some recent update.
Who in the forum might have an confirmation on this?
This kind of a big issue, right? :-)
-
Hi
No problem for the delay :-)
I am running the OSX version so I can't manually delete and re-download the blockchain?
You can.
I don't have access to an osx machine at the moment. If I had to guess I'd say the folders chain and peers.leveldb are at:
~/Library/Application Support/BitShares
So navigate there, and delete only chain and peers.leveldb.
To be on the safe side, you could make a copy of the entire BitShares folder on your desktop before deleting anything.
Then just re-launch the client.
-
Hi
No problem for the delay :-)
I am running the OSX version so I can't manually delete and re-download the blockchain?
You can.
I don't have access to an osx machine at the moment. If I had to guess I'd say the folders chain and peers.leveldb are at:
~/Library/Application Support/BitShares
So navigate there, and delete only chain and peers.leveldb.
To be on the safe side, you could make a copy of the entire BitShares folder on your desktop before deleting anything.
Then just re-launch the client.
Just did it.
I took an awful long time before the client restarted so I guess the block chain was re-downloaded.
The balance remained the same.
I once again imported the wallet key successfully, but nothing changes :-(((
-
Hi
No problem for the delay :-)
I am running the OSX version so I can't manually delete and re-download the blockchain?
You can.
I don't have access to an osx machine at the moment. If I had to guess I'd say the folders chain and peers.leveldb are at:
~/Library/Application Support/BitShares
So navigate there, and delete only chain and peers.leveldb.
To be on the safe side, you could make a copy of the entire BitShares folder on your desktop before deleting anything.
Then just re-launch the client.
Just did it.
I took an awful long time before the client restarted so I guess the block chain was re-downloaded.
The balance remained the same.
I once again imported the wallet key successfully, but nothing changes :-(((
Are you sure you had pts before february 28?
can you type getinfo in the console and post here the info?
This is really weird
-
Hi
No problem for the delay :-)
I am running the OSX version so I can't manually delete and re-download the blockchain?
You can.
I don't have access to an osx machine at the moment. If I had to guess I'd say the folders chain and peers.leveldb are at:
~/Library/Application Support/BitShares
So navigate there, and delete only chain and peers.leveldb.
To be on the safe side, you could make a copy of the entire BitShares folder on your desktop before deleting anything.
Then just re-launch the client.
Just did it.
I took an awful long time before the client restarted so I guess the block chain was re-downloaded.
The balance remained the same.
I once again imported the wallet key successfully, but nothing changes :-(((
Are you sure you had pts before february 28?
can you type getinfo in the console and post here the info?
This is really weird
No I did not have the before february 28. But I should receive some BTS (merger VOTE/DNS) because I had PTS during the november 5 snapshot?
I've read somewhere I am entitled to (amount of PTS @ november 5 x 567) BTS.
This what I get after typing getinfo in the console:
>> getinfo
{
"blockchain_head_block_num": 1503000,
"blockchain_head_block_age": "6 seconds old",
"blockchain_head_block_timestamp": "2015-01-12T06:58:10",
"blockchain_average_delegate_participation": "100.00 %",
"blockchain_confirmation_requirement": 1,
"blockchain_share_supply": "2,498,242,645.29152 BTS",
"blockchain_blocks_left_in_round": 82,
"blockchain_next_round_time": "at least 14 minutes in the future",
"blockchain_next_round_timestamp": "2015-01-12T07:11:50",
"blockchain_random_seed": "48e0381027b8107a9c6b2fde6c594d86270843cf",
"client_data_dir": "/Users/marcsegers/Library/Application Support/BitShares",
"client_version": "v0.4.27.2",
"network_num_connections": 8,
"network_num_connections_max": 200,
"network_chain_downloader_running": false,
"network_chain_downloader_blocks_remaining": null,
"ntp_time": "2015-01-12T06:58:16",
"ntp_time_error": 0.020735,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "2015-01-23T20:40:54",
"wallet_last_scanned_block_timestamp": "2014-07-19T03:18:50",
"wallet_scan_progress": "0.57 %",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
-
No I did not have the before february 28. But I should receive some BTS (merger VOTE/DNS) because I had PTS during the november 5 snapshot?
I've read somewhere I am entitled to (amount of PTS @ november 5 x 567) BTS.
The BTS from the merger don't show up in your regular balance yet. You can check your shares by entering the command wallet_check_sharedrop in the console. You have to divide the displayed numbers by 100000 to get the BTS amount.
Also, the factor is much lower than 567, more like 45 or so. There's a thread somewhere in the forum that lists what you have to expect.
-
I've read somewhere I am entitled to (amount of PTS @ november 5 x 567) BTS.
PTS x 567 sharedrop was for the february 28 snapshot
-
No I did not have the before february 28. But I should receive some BTS (merger VOTE/DNS) because I had PTS during the november 5 snapshot?
I've read somewhere I am entitled to (amount of PTS @ november 5 x 567) BTS.
The BTS from the merger don't show up in your regular balance yet. You can check your shares by entering the command wallet_check_sharedrop in the console. You have to divide the displayed numbers by 100000 to get the BTS amount.
Also, the factor is much lower than 567, more like 45 or so. There's a thread somewhere in the forum that lists what you have to expect.
I get 3 different numbers. What is the difference between them?
-
No I did not have the before february 28. But I should receive some BTS (merger VOTE/DNS) because I had PTS during the november 5 snapshot?
I've read somewhere I am entitled to (amount of PTS @ november 5 x 567) BTS.
The BTS from the merger don't show up in your regular balance yet. You can check your shares by entering the command wallet_check_sharedrop in the console. You have to divide the displayed numbers by 100000 to get the BTS amount.
Also, the factor is much lower than 567, more like 45 or so. There's a thread somewhere in the forum that lists what you have to expect.
I get 3 different numbers. What is the difference between them?
My guess would be they are for DNS, AGS and PTS or something like that. Or for three different addresses? Anyway, in the end you should receive the sum of the three.
-
No I did not have the before february 28. But I should receive some BTS (merger VOTE/DNS) because I had PTS during the november 5 snapshot?
I've read somewhere I am entitled to (amount of PTS @ november 5 x 567) BTS.
The BTS from the merger don't show up in your regular balance yet. You can check your shares by entering the command wallet_check_sharedrop in the console. You have to divide the displayed numbers by 100000 to get the BTS amount.
Also, the factor is much lower than 567, more like 45 or so. There's a thread somewhere in the forum that lists what you have to expect.
I get 3 different numbers. What is the difference between them?
My guess would be they are for DNS, AGS and PTS or something like that. Or for three different addresses? Anyway, in the end you should receive the sum of the three.
Any idea when these BTS will appear in the balance?
-
Any idea when these BTS will appear in the balance?
https://bitsharestalk.org/index.php?topic=11350.msg166503#msg166503
-
No I did not have the before february 28. But I should receive some BTS (merger VOTE/DNS) because I had PTS during the november 5 snapshot?
I've read somewhere I am entitled to (amount of PTS @ november 5 x 567) BTS.
The BTS from the merger don't show up in your regular balance yet. You can check your shares by entering the command wallet_check_sharedrop in the console. You have to divide the displayed numbers by 100000 to get the BTS amount.
Also, the factor is much lower than 567, more like 45 or so. There's a thread somewhere in the forum that lists what you have to expect.
I get 3 different numbers. What is the difference between them?
My guess would be they are for DNS, AGS and PTS or something like that. Or for three different addresses? Anyway, in the end you should receive the sum of the three.
So I need to wait until the next release to fix this issue?
-
No I did not have the before february 28. But I should receive some BTS (merger VOTE/DNS) because I had PTS during the november 5 snapshot?
I've read somewhere I am entitled to (amount of PTS @ november 5 x 567) BTS.
The BTS from the merger don't show up in your regular balance yet. You can check your shares by entering the command wallet_check_sharedrop in the console. You have to divide the displayed numbers by 100000 to get the BTS amount.
Also, the factor is much lower than 567, more like 45 or so. There's a thread somewhere in the forum that lists what you have to expect.
I get 3 different numbers. What is the difference between them?
My guess would be they are for DNS, AGS and PTS or something like that. Or for three different addresses? Anyway, in the end you should receive the sum of the three.
So I need to wait until the next release to fix this issue?
If you have pts after february 28 then yes, you have to update to 0.5 version and wait a few days for the fork or whatever it's called. If you had pts before february 28 then try the new version and tell us what happens(I think your problem will be solved)
-
No I did not have the before february 28. But I should receive some BTS (merger VOTE/DNS) because I had PTS during the november 5 snapshot?
I've read somewhere I am entitled to (amount of PTS @ november 5 x 567) BTS.
The BTS from the merger don't show up in your regular balance yet. You can check your shares by entering the command wallet_check_sharedrop in the console. You have to divide the displayed numbers by 100000 to get the BTS amount.
Also, the factor is much lower than 567, more like 45 or so. There's a thread somewhere in the forum that lists what you have to expect.
I get 3 different numbers. What is the difference between them?
My guess would be they are for DNS, AGS and PTS or something like that. Or for three different addresses? Anyway, in the end you should receive the sum of the three.
So I need to wait until the next release to fix this issue?
If you have pts after february 28 then yes, you have to update to 0.5 version and wait a few days for the fork or whatever it's called. If you had pts before february 28 then try the new version and tell us what happens(I think your problem will be solved)
Installed the 0.5 OSX version. I waited for the mentioned block. But the command "wallet_collect_vesting_balances" isn't f***** working. I still can't see any correct balance.
Honestly, this whole thing is starting to piss me off…
-
Do you have more than one account in your wallet? Only the account that you imported your wallet works.
EDIT
wallet_collect_vesting_balances your_account
wallet_collect_vested_balances your_account
Also run the getinfo command to check if your wallet is fully synched and if your transactions are 100% scanned.
If you still have problems post your error messages and someone will be able to help.
-
Installed the 0.5 OSX version. I waited for the mentioned block. But the command "wallet_collect_vesting_balances" isn't f***** working. I still can't see any correct balance.
Honestly, this whole thing is starting to piss me off…
Try again. You posted more than 1 hour before the hardfork block.
-
>> getinfo
{
"blockchain_head_block_num": 1583626,
"blockchain_head_block_age": "5 seconds old",
"blockchain_head_block_timestamp": "2015-01-21T17:21:40",
"blockchain_average_delegate_participation": "100.00 %",
"blockchain_confirmation_requirement": 1,
"blockchain_share_supply": "2,498,222,380.14517 BTS",
"blockchain_blocks_left_in_round": 54,
"blockchain_next_round_time": "at least 9 minutes in the future",
"blockchain_next_round_timestamp": "2015-01-21T17:30:40",
"blockchain_random_seed": "214a244f405a496c2d725976c4e86709397f2273",
"client_data_dir": "/Users/Library/Application Support/BitShares",
"client_version": "v0.5.1",
"network_num_connections": 18,
"network_num_connections_max": 200,
"network_chain_downloader_running": false,
"network_chain_downloader_blocks_remaining": null,
"ntp_time": "2015-01-21T17:21:45",
"ntp_time_error": 0.0028370000000000001,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "2015-02-02T07:04:56",
"wallet_last_scanned_block_timestamp": "2015-01-21T17:21:40",
"wallet_scan_progress": "100.00 %",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
}
-
>> wallet_collect_vesting_balances
Error: invalid command "wallet_collect_vesting_balances"
Also if I put my account name after the wallet_collect_vesting_balances command , I get the same error message every time
-
I got the message the keys from the PTS wallet were imported successfully
When I wanted to claim my new PTS from my old PTS with the new PTS client, I didn't have any problem.
The new PTS balance showed up right away.
What else can I do????
-
Try
wallet_collect_vested_balances
>> wallet_collect_vesting_balances
Error: invalid command "wallet_collect_vesting_balances"
Also if I put my account name after the wallet_collect_vesting_balances command , I get the same error message every time
-
{
"index": 0,
"record_id": "c8b75913b1e9cb06cda03b908eaf97a30b44c95d",
"block_num": 0,
"is_virtual": false,
"is_confirmed": false,
"is_market": false,
"trx": {
"expiration": "2015-01-21T18:42:19",
"slate_id": null,
"operations": [{
"type": "withdraw_op_type",
"data": {
"balance_id": "BTSQ75tXimtbECXHMWdKi8nUfTSXsvnJHsAF",
"amount": 527599278,
"claim_input_data": ""
}
},{
"type": "withdraw_op_type",
"data": {
"balance_id": "BTSMXwHTaFzxrvqDxanziLoLWo5vUwvL6JrE",
"amount": 70393325,
"claim_input_data": ""
}
},{
"type": "withdraw_op_type",
"data": {
"balance_id": "BTSLuQZGdGZjycDwNZB7zBJWNKpNRawMP5q6",
"amount": 116088496,
"claim_input_data": ""
}
},{
"type": "deposit_op_type",
"data": {
"amount": 714031099,
"condition": {
"asset_id": 0,
"slate_id": 0,
"type": "withdraw_signature_type",
"data": {
"owner": "BTSnpT8uLDMHAfKafBjb8vhJVA9mPwkpbx3",
"memo": {
"one_time_key": "BTS7jVkCoUXqTTXFSNPd6XMjED5q1ej4YoUoiYLAXYa5mmEncvNNm",
"encrypted_memo_data": "d3b2977f88ef5a09e188ffa10b6766d3b28f8a6ee6ed16924663a321286f1a4992f22cec3b718445cf11eb30cd20355f5531b298906f061a1f3dd3188e8b864f"
}
}
}
}
}
],
"signatures": [
"1f60df91cc144c9142a7ad6dd2e7fc8ef2c6bed4c9899afe7cdcec395058c864d80758b604be43731f81f63803dea434efd7fceab4f7a72f376185264864b84644"
]
},
"ledger_entries": [{
"from_account": "BTS7tjXfP5y26jGAPbJTMoX8mRP4MuA4H5Jgb6dUHpvPFCJBSHwMo",
"to_account": "BTS7tjXfP5y26jGAPbJTMoX8mRP4MuA4H5Jgb6dUHpvPFCJBSHwMo",
"amount": {
"amount": 714031099,
"asset_id": 0
},
"memo": "collect vested",
"memo_from_account": null
}
],
"fee": {
"amount": 50000,
"asset_id": 0
},
"created_time": "2015-01-21T17:42:20",
"received_time": "2015-01-21T17:42:20",
"extra_addresses": []
}
-
That means you have got 7140.31099bts till now.
{
"index": 0,
"record_id": "c8b75913b1e9cb06cda03b908eaf97a30b44c95d",
"block_num": 0,
"is_virtual": false,
"is_confirmed": false,
"is_market": false,
"trx": {
"expiration": "2015-01-21T18:42:19",
"slate_id": null,
"operations": [{
"type": "withdraw_op_type",
"data": {
"balance_id": "BTSQ75tXimtbECXHMWdKi8nUfTSXsvnJHsAF",
"amount": 527599278,
"claim_input_data": ""
}
},{
"type": "withdraw_op_type",
"data": {
"balance_id": "BTSMXwHTaFzxrvqDxanziLoLWo5vUwvL6JrE",
"amount": 70393325,
"claim_input_data": ""
}
},{
"type": "withdraw_op_type",
"data": {
"balance_id": "BTSLuQZGdGZjycDwNZB7zBJWNKpNRawMP5q6",
"amount": 116088496,
"claim_input_data": ""
}
},{
"type": "deposit_op_type",
"data": {
"amount": 714031099,
"condition": {
"asset_id": 0,
"slate_id": 0,
"type": "withdraw_signature_type",
"data": {
"owner": "BTSnpT8uLDMHAfKafBjb8vhJVA9mPwkpbx3",
"memo": {
"one_time_key": "BTS7jVkCoUXqTTXFSNPd6XMjED5q1ej4YoUoiYLAXYa5mmEncvNNm",
"encrypted_memo_data": "d3b2977f88ef5a09e188ffa10b6766d3b28f8a6ee6ed16924663a321286f1a4992f22cec3b718445cf11eb30cd20355f5531b298906f061a1f3dd3188e8b864f"
}
}
}
}
}
],
"signatures": [
"1f60df91cc144c9142a7ad6dd2e7fc8ef2c6bed4c9899afe7cdcec395058c864d80758b604be43731f81f63803dea434efd7fceab4f7a72f376185264864b84644"
]
},
"ledger_entries": [{
"from_account": "BTS7tjXfP5y26jGAPbJTMoX8mRP4MuA4H5Jgb6dUHpvPFCJBSHwMo",
"to_account": "BTS7tjXfP5y26jGAPbJTMoX8mRP4MuA4H5Jgb6dUHpvPFCJBSHwMo",
"amount": {
"amount": 714031099,
"asset_id": 0
},
"memo": "collect vested",
"memo_from_account": null
}
],
"fee": {
"amount": 50000,
"asset_id": 0
},
"created_time": "2015-01-21T17:42:20",
"received_time": "2015-01-21T17:42:20",
"extra_addresses": []
}
-
That means you have got 7140.31099bts till now.
{
"index": 0,
"record_id": "c8b75913b1e9cb06cda03b908eaf97a30b44c95d",
"block_num": 0,
"is_virtual": false,
"is_confirmed": false,
"is_market": false,
"trx": {
"expiration": "2015-01-21T18:42:19",
"slate_id": null,
"operations": [{
"type": "withdraw_op_type",
"data": {
"balance_id": "BTSQ75tXimtbECXHMWdKi8nUfTSXsvnJHsAF",
"amount": 527599278,
"claim_input_data": ""
}
},{
"type": "withdraw_op_type",
"data": {
"balance_id": "BTSMXwHTaFzxrvqDxanziLoLWo5vUwvL6JrE",
"amount": 70393325,
"claim_input_data": ""
}
},{
"type": "withdraw_op_type",
"data": {
"balance_id": "BTSLuQZGdGZjycDwNZB7zBJWNKpNRawMP5q6",
"amount": 116088496,
"claim_input_data": ""
}
},{
"type": "deposit_op_type",
"data": {
"amount": 714031099,
"condition": {
"asset_id": 0,
"slate_id": 0,
"type": "withdraw_signature_type",
"data": {
"owner": "BTSnpT8uLDMHAfKafBjb8vhJVA9mPwkpbx3",
"memo": {
"one_time_key": "BTS7jVkCoUXqTTXFSNPd6XMjED5q1ej4YoUoiYLAXYa5mmEncvNNm",
"encrypted_memo_data": "d3b2977f88ef5a09e188ffa10b6766d3b28f8a6ee6ed16924663a321286f1a4992f22cec3b718445cf11eb30cd20355f5531b298906f061a1f3dd3188e8b864f"
}
}
}
}
}
],
"signatures": [
"1f60df91cc144c9142a7ad6dd2e7fc8ef2c6bed4c9899afe7cdcec395058c864d80758b604be43731f81f63803dea434efd7fceab4f7a72f376185264864b84644"
]
},
"ledger_entries": [{
"from_account": "BTS7tjXfP5y26jGAPbJTMoX8mRP4MuA4H5Jgb6dUHpvPFCJBSHwMo",
"to_account": "BTS7tjXfP5y26jGAPbJTMoX8mRP4MuA4H5Jgb6dUHpvPFCJBSHwMo",
"amount": {
"amount": 714031099,
"asset_id": 0
},
"memo": "collect vested",
"memo_from_account": null
}
],
"fee": {
"amount": 50000,
"asset_id": 0
},
"created_time": "2015-01-21T17:42:20",
"received_time": "2015-01-21T17:42:20",
"extra_addresses": []
}
Indeed the balance is updated now.
What do you mean with 'till now'?
Will I receive some more?
thanks
-
7140 BTS is an awful low amount looking at the amount of pts I bought back then
-
7140 BTS is an awful low amount looking at the amount of pts I bought back then
Those 7140 bts are your sharedrop from november 5 until today, you will continue to recieve bitshares for the next 21,5 months everytime you run the command in the console, at a rate of (if my calculations are correct) 92 bts per day, you can claim them hourly, daily, monthly, whenever you want.
-
I updated my client to 0.5.1 -- now when I try to import my PTS wallet, it crashes. Something is up =/
-
7140 BTS is an awful low amount looking at the amount of pts I bought back then
Those 7140 bts are your sharedrop from november 5 until today, you will continue to recieve bitshares for the next 21,5 months everytime you run the command in the console, at a rate of (if my calculations are correct) 92 bts per day, you can claim them hourly, daily, monthly, whenever you want.
Thank you for the information.
What is the calculation behind your answer?
thanks
-
Now you just got about 10% of your total sharedrop bts.
7140 BTS is an awful low amount looking at the amount of pts I bought back then
-
7140 BTS is an awful low amount looking at the amount of pts I bought back then
it's "vested" over 2!! years .. do you can do the same command every day the next two years and will get a 1/(2*365)-th of your total vested amount
wallet_check_sharedrop shows the total amount you can get
-
7140 BTS is an awful low amount looking at the amount of pts I bought back then
Those 7140 bts are your sharedrop from november 5 until today, you will continue to recieve bitshares for the next 21,5 months everytime you run the command in the console, at a rate of (if my calculations are correct) 92 bts per day, you can claim them hourly, daily, monthly, whenever you want.
Thank you for the information.
What is the calculation behind your answer?
thanks
7140 bts / (days that have past since 5th of November)
Practically, you can run wallet_collect_vested_balances your account right now and then again in one hour or in one day in order to see what is your hourly daily sharedrop.
-
I have installed client 0.5.3 recently and reimport my wallet backup. I am able to see my balance after I import my wallet backup (means cannot see it before import and after installation of 0.5.3).
However, after I type the following command I get an exception:
>> wallet_account_list_public_keys hpm
10 assert_exception: Assert Exception
my->is_unique_account(account_name):
{}
bitshares wallet.cpp:3941 bts::wallet::wallet::get_owner_public_key
{"account_name":"hpm"}
bitshares wallet.cpp:3958 bts::wallet::wallet::get_owner_public_key
{}
bitshares common_api_client.cpp:5199 bts::rpc_stubs::common_api_client::wallet_account_list_public_keys
{"command":"wallet_account_list_public_keys"}
bitshares cli.cpp:629 bts::cli::detail::cli_impl::execute_command
Here is my info
>> getinfo
{
"blockchain_head_block_num": 1621018,
"blockchain_head_block_age": "4 seconds old",
"blockchain_head_block_timestamp": "2015-01-26T02:55:00",
"blockchain_average_delegate_participation": "100.00 %",
"blockchain_confirmation_requirement": 1,
"blockchain_share_supply": "2,498,675,010.54306 BTS",
"blockchain_blocks_left_in_round": 32,
"blockchain_next_round_time": "at least 5 minutes in the future",
"blockchain_next_round_timestamp": "2015-01-26T03:00:20",
"blockchain_random_seed": "70e002f44e2d6edb657907010393e7bf12aa708a",
"client_data_dir": "C:/Users/hupm1/AppData/Roaming/BitShares",
"client_version": "v0.5.3",
"network_num_connections": 19,
"network_num_connections_max": 200,
"network_chain_downloader_running": false,
"network_chain_downloader_blocks_remaining": null,
"ntp_time": "2015-01-26T02:55:04",
"ntp_time_error": -0.044019000000000003,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "2015-02-06T16:36:02",
"wallet_last_scanned_block_timestamp": "2014-07-22T15:08:00",
"wallet_scan_progress": "11.73 %",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
}
Any one can help to look at the exception? What's wrong with my account? I have PTS account before Feb 2014.
-
And the most interesting thing is after I import my key, the client ask me to change me account name, because hpm is already registered on the network. When I click confirm to change, the button stuck there forever.
-
This may have nothing to to with your problem but "wallet_scan_progress": "11.73 %" should be 100%
Run again getinfo and if it's not 100% run getinfo again in one minute, if the value is increased don't close your wallet until it gets to 100% (run getinfo periodically to check the percentage)
If it's stuck to a number and is not rising then run rescan and give it some time to do the rescanning.
-
And the most interesting thing is after I import my key, the client ask me to change me account name, because hpm is already registered on the network. When I click confirm to change, the button stuck there forever.
You will have to use "wallet_account_rename" console command if GUI button is not working.
-
The balance is still not correct with my client. I run all the following commands suggested, any one can take a look? My balance only show 313.77209 BTS which is collect vested. I should have 9,042 BTS there.
>> wallet_account_list_public_keys hpm
[{
"hex": "0229727c21ee94ebb01251268353eb43e8a4edf62c18f03346d3b75ca96580bab9",
"native_pubkey": "BTS5Ck4qKbqgDn41uxkJSvyXaz4KTLtmyV3kyMunHv7HUuMiRBhcX",
"native_address": "BTS4yR492id1xxvgq9Q2kSD9zGxA4bdTmZSK",
"pts_normal_address": "Pti3s8jZWuapTEnTGQDT3DXs5Q634MZnxE",
"pts_compressed_address": "Pf1hXvYVrSVaU8yoyADcD5rzvovqJG8ejE",
"btc_normal_address": "1MnGj43RkodkexybtuZbtCHoq9fDJe8rCY",
"btc_compressed_address": "185vPqrN6LYWfsAxbfZm44cwgZW1Vq1MQn"
},{
"hex": "0357a1e7152fd7396ab72abd650cc1fa4e89cad812a04ab82e9423d047cc996b14",
"native_pubkey": "BTS7Vpyxo2o7CorEcCd4K376ibuczKvyKwUPBumscsLeje38Zd3eL",
"native_address": "BTSHrHJoeTQfAqPTA2ik4t2K8HxxbHdRpnU6",
"pts_normal_address": "PgdnJSUr52AbCo6fK9Khk29nupC4VgWfVh",
"pts_compressed_address": "PrAsgx7TJ9fFAKuvLNvZNHefSw9r3mKt6C",
"btc_normal_address": "19i1AMniJvDXQXHowefrazujfZmEkQKK1t",
"btc_compressed_address": "1KF6YsRKY3iBN474xtGiDGQcCgj2FTzjJX"
}
]
>> wallet_check_sharedrop
[{
"original_address": "PYgpUhLjTgfEsVaW2N5oR9Gbgn9JxTai3r",
"original_balance": 209029945
},{
"original_address": "PYgpUhLjTgfEsVaW2N5oR9Gbgn9JxTai3r",
"original_balance": 45993186
},{
"original_address": "PYgpUhLjTgfEsVaW2N5oR9Gbgn9JxTai3r",
"original_balance": 27889183
}
]
>> wallet_collect_vested_balances hpm
20010 insufficient_funds: insufficient funds
{"account_name":"hpm"}
bitshares wallet.cpp:2098 bts::wallet::wallet::collect_withdraw_types
{"account_name":"hpm","sign":true}
bitshares wallet.cpp:2141 bts::wallet::wallet::collect_withdraw_types
{}
bitshares common_api_client.cpp:6120 bts::rpc_stubs::common_api_client::wallet_collect_vested_balances
{"command":"wallet_collect_vested_balances"}
bitshares cli.cpp:629 bts::cli::detail::cli_impl::execute_command
>> getinfo
{
"blockchain_head_block_num": 1648402,
"blockchain_head_block_age": "6 seconds old",
"blockchain_head_block_timestamp": "2015-01-29T07:11:10",
"blockchain_average_delegate_participation": "94.39 %",
"blockchain_confirmation_requirement": 1,
"blockchain_share_supply": "2,499,076,931.43951 BTS",
"blockchain_blocks_left_in_round": 19,
"blockchain_next_round_time": "at least 3 minutes in the future",
"blockchain_next_round_timestamp": "2015-01-29T07:14:20",
"blockchain_random_seed": "24d216f7556cdbc17bcd81a6bd10878cbfa9030c",
"client_data_dir": "C:/Users/hupm1/AppData/Roaming/BitShares",
"client_version": "v0.5.3",
"network_num_connections": 20,
"network_num_connections_max": 200,
"network_chain_downloader_running": false,
"network_chain_downloader_blocks_remaining": null,
"ntp_time": null,
"ntp_time_error": null,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "2015-02-09T20:39:35",
"wallet_last_scanned_block_timestamp": "2015-01-29T07:11:10",
"wallet_scan_progress": "100.00 %",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
}
-
The balance is still not correct with my client. I run all the following commands suggested, any one can take a look? My balance only show 313.77209 BTS which is collect vested. I should have 9,042 BTS there.
>> wallet_check_sharedrop
[{
"original_address": "PYgpUhLjTgfEsVaW2N5oR9Gbgn9JxTai3r",
"original_balance": 209029945
},{
"original_address": "PYgpUhLjTgfEsVaW2N5oR9Gbgn9JxTai3r",
"original_balance": 45993186
},{
"original_address": "PYgpUhLjTgfEsVaW2N5oR9Gbgn9JxTai3r",
"original_balance": 27889183
}
]
You have to divide those number by 100000 to get your actual sharedrop in BTS, i. e. 2090 + 459 + 278 ~= 2800 BTS. For this, ~300 BTS collected seems reasonable after ~2.5 months. Apparently you have imported only one PTS private key. The corresponding address holds ~21 PTS (see https://coinplorer.com/PTS/Addresses/PYgpUhLjTgfEsVaW2N5oR9Gbgn9JxTai3r ), which makes the sharedrop display plausible.
What makes you think there should be ~9000 BTS?