Everyone please try this version and let us know if the crashing is fixed: https://github.com/dacsunlimited/qt_wallet/releases/tag/v0.2.3.1

Everyone please try this version and let us know if the crashing is fixed: https://github.com/dacsunlimited/qt_wallet/releases/tag/v0.2.3.1

Each share can always vote for 101 in the blockchain.

If you choose to use the vote_random strategy when transferring, it will limit your transfer to a slate size of at most 33 for increased privacy.

Quote from: G1ng3rBr34dM4n on July 23, 2014, 01:40:58 am

Quote from: bytemaster on July 21, 2014, 03:57:07 am

Quote from: BTS Ninja on July 21, 2014, 02:10:59 am

@BM

Correct me if I was wrong. I am using the Windows package. When I was tried to move the wallet from one PC to another PC. I go to roaming folder and copy the wallet folder inside the BitShares X folder along. I saw that it works fine. Is it a good way to move/backup/restore the wallet?

I see that we have the backup option to export the .json file. I think it is used for backup at this point of time. The import function doesnt work yet?

Import works, it is just not user-friendly.  Your approach also works.

Can someone explain how to do this (through the command line??). 

My wallet crashed on one computer and I couldn't re-install and get it to reopen (Mac version, reference post here: https://bitsharestalk.org/index.php?topic=5968.msg79809#msg79809  At least one other is having this problem too).

Able to get wallet operational on another computer but can't figure out how to import .json file.

HELP 

edit: I also wanted to mention this is for a registered account on the blockchain, if it makes any difference.

Alright an update on my attempts to import the .json file:

Tried to use: wallet_create_from_json <json_filename> <wallet_name> <imported_wallet_passphrase>

and then received:

Code: [Select]

wallet must be open to execute this command. You can:
(o) Open an existing wallet
(c) Create a new wallet
(q) Abort command
Command aborted
So I type: (c) and get

Code: [Select]

>> (c)

Error: invalid command "(c)"
If anyone else has figure this out, let me know... I'm not a CS savvy guy, but I'd appreciate any help.  Happy to tip you. 

This should not ask you to open a wallet if you do wallet_create_from_json. Can you copy and paste the entire series of commands and their output when you try to import the json file?

Quote from: xeroc on July 23, 2014, 04:43:14 am

Quote from: changematey on July 23, 2014, 04:38:05 am

How about an option for "holding" even though if it means zombie btsx accounts for year or two.

I you don't move you btsx once a year you might be forced to pay a 5% inactivity fee .. just FYI
http://wiki.bitshares.org/index.php/Inactivity_Fees

Would this also apply for unclaimed btsx?  For example AGS allocation not yet imported?

Yes it would apply; there is no such thing as unclaimed BTSX in the chain.

Quote from: bobmaloney on July 22, 2014, 07:30:55 pm

Can we get a quick how-to for exporting our Keyhotee private keys and importing them to BTSX.

Many thanks.

agree！

Done!

http://wiki.bitshares.org/index.php/BitShares_X_Solutions#How_to_import_Keyhotee_IDs

Great! Thanks for posting links to code!

Question:

Code: [Select]

new_entry = false;
 +                     // TODO: We should probably really have a map of asset ids to amounts per ledger entry
 +                     if( entry.amount.asset_id == amount.asset_id )
 +                         entry.amount += amount;
 +                     else if( entry.amount.amount == 0 )
 +                         entry.amount = amount;

Will you check this logic.

I see that this will fail when transferring assets other than the base asset, as I must have realized at some level before relegating the thought to the TODO there. Good catch! Will think how to address this.

Transactions can be almost arbitrarily complex but to keep meaningful records in our simple wallet we are making strong simplifying assumptions for now. We also have the problem that everyone already has a wallet using a certain format for storing their existing transaction records.

And also - are there tests associated with this code? I know it's a lot to ask for but we should have good integration tests that try all kinds of things.

E.g. have you thoroughly tested with multiple assets. Or able to simulate a missing transaction on the sending/receiving end, and see how the system behaves?

No tests yet, but I intend to write them when there is some time. Still many other fires to put out at the moment.

I have not thoroughly tested with multiple assets / market functionality yet, as is clear from the problem above. Missing transfers of the base asset on sending and receiving side are correctly reconstructed, however.


I also forgot to mention that in the OP, you seem to have been affected by problems with transaction scanning combined with an issue that causes transactions to be stuck pending. This is a known issue but we are still tracking down the cause. Sometimes they get unstuck after some random period of time, so be cautious about resending transactions.

I have been working on the transaction history and wallet rescanning code:

• https://github.com/BitShares/bitshares_toolkit/compare/bcd3d69772...7291385d48
• https://github.com/BitShares/bitshares_toolkit/compare/d43c3982a9...fc69f9efa1
• https://github.com/BitShares/bitshares_toolkit/compare/c09d3fecb1...f998c122ad
• https://github.com/BitShares/bitshares_toolkit/compare/23372db089...dc1d28ec71
• https://github.com/BitShares/bitshares_toolkit/commit/0e41da25a206518588e8b6deb5a5db3e0ad95b87

There were quite a number of problems with the wallet transaction scanning causing missing entries, incorrect balances, silently failing rescans, etc. In my testing so far, transaction history reconstruction works much better now. I am able to delete every transaction record (withdrawals, deposits, account operations, asset operations) from my wallet and it correctly brings them all back (sans any irrecoverable information due to TITAN). More testing is required but I think we might be able to fix your issues.

These fixes will be in the next release. You guys will have to do a full rescan (backup your wallet first, just in case) and we can see if it fixes your transaction histories.