off topic
i wonder what imapct for  mass adoption the growing sice of the wallet will have
if a average useres pc with lets say 4 to 8 gb working space and a 120 gb disc and a series 4 procesor cant handle it

my procesor is while downloading the blockchain most of the time at 100% and i added already a extra cooling pad

right now the bitshare is less then a year runnning and only a few use it
what size will it have when millions use it , trade ........... every day
and if there is a upgrade for the wallet you need to resync the chain from day one?

i daubt many average useres or new users will have the patience to wait for days till its synct

i wonder if there is a way to make it smaler and faster
i read something about ethereum that they use a snapshot on which all sort of delegates or miners agree and put it in a codepoint
i am not a expert but as i understood it :
make a picture of the agreed chain part seel it and use that as a startpoint for the wallet

it reminds me of music files and how they developed mp3 technique i wonder if that is posible with the blockchain

It's said that average users will use the light wallet or web wallet in the future.

Quote from: lastagile on April 08, 2015, 11:56:34 am

anyone knows when the 0.9will release？I have some asset can not found. Now I need to cover the short with that money.

Have you tried importing your wallet into 0.8?  I had no issues receiving shares from NOTES.

The problem is that 0.8 has an issue while recovering/regenerating active key.

Hey there, I'm having the same problem where I'm stuck at 2074788.

I'm fairly non technical and don't get how to replace the checkpoints.json file as mentioned above.  Are there instructions on how to do this somewhere? Or another solution?

Thanks for any help!

That checkpoints.json doesn't work for block 2074788 issue. It only works after block 2113000.

Try this: http://wiki.bitshares.org/index.php/BitShares/Chain-Server

Quote from: marcelus on April 02, 2015, 01:21:36 pm

Quote from: abit on March 30, 2015, 03:14:02 pm

Yes you are on a fork. Reindex doesn't work in this case.
You need to remove the chain folder and resync.
Try replace your checkpoints.json with the one in this post https://bitsharestalk.org/index.php?topic=15218.msg196858#msg196858 , then resync or reindex.

I did this, removed a chain server and reindexed and now I'm stuck at block 2073989. I seem to have regressed!

Fixed it. Resynced from wackou's chain server. Worked quite quickly.

Glad to hear your problem get solved.
I was wrong. Re-index doesn't work indeed.
I'm sorry for that. I modified my post again.

//Edit:
Just notice that 2073989 (in your post) and 2074788 (in OP) are both before the 0.8.0 hard fork (at 2113000), so it could be other forks.

I recently hit some issues with 0.8.

I tried enabling RPC and this triggered a full blockchain re-download which took a few hours.
While this was happening, I set the logout automatically to a really big number like 40000000000 or something. This triggered a bug rendering the wallet completely unusable with the timing out screen rapidly appearing and disappearing. I couldn't fix this from removing the config etc and in the end had to restore from a backup wallet.

It could be a bug about bound overflow. I usually set the timeout to 99999999 with no problem (around 3 years).

The wallet parameter is stored in wallet database, not in config.json, so deleting the config file doesn't help.

Just a note, when the GUI getting unusable, you could try the command line if you're under linux/windows.

Quote from: abit on April 03, 2015, 04:53:36 pm

In the coming release (0.9.0, now testing in dvs), expired shorts will sell at feed price only, is it really good?
In current release(0., expired shorts will sell above 90% of feed price, same as margin calls. I think this feature is reasonable.
Any discussion before? Please give me a link, thanks.

We discussed it both ways and there are pros and cons.  If no one is selling their BitUSD then shorts will be hurt and thus they may not short again in the future.  Absent a reliable market maker the feed protection protects all shorts.

Just some thoughts.

The market will become less efficient with the new matching rule. If no one wants to buy BTS at feed price, the expired orders will probably hang there for a long time and won't take priority while matching. People could short/bid at a lower price and happily get matched with low-priced ask orders.

With 0.8, if some huge shorts expired, many traders will see it as a chance to buy cheap BTS and thus the market works. With 0.9, perhaps small traders are not willing to fill those huge orders. If a whale wants to buy the expired shorts (BTS) at a lower price, she will probably dump at btc38 to lower the feed price first. The result is similar.

We protect shorts which obey the rules (cover before expire).

Anyway, the market speaks, let's see what will happen.

Best if people can drag and drop the elements/panels to anywhere and any size as she/he want, and save as her/his favorite theme, and can switch among themes easily 

Quote from: monsterer on March 30, 2015, 10:18:21 am

My win 0.8.0-a (and 0.8.0 builds) are stuck on the wrong fork, is there anything I can do without having to delete and regrab the entire chain?

restart with

Code: [Select]

--rebuild-index
may only work with the bitshares_client.exe (nonGUI)

I think it wont work if he is more than 360 blocks after the hard fork block.
Upgrade to 0.8.1 and resync should work.

//Edit:
Reindex would work, but only after upgraded to 0.8.1 or updated checkpoints.json like this post https://bitsharestalk.org/index.php?topic=15218.msg196858#msg196858 .
With 0.8.0 and old checkpoints.json, the client will still think the wrong fork is valid, and will stuck again.