Did you include the following line between cmake . and make?

export LC_ALL="en_US.UTF-8"

I think there are more recent build instructions in the github repo which you can find here

https://github.com/BitShares/bitshares/blob/bts/0.5.0/BUILD_UBUNTU.md

You may have to upgrade to the new version soon though.

I would start over, clone to a new directory, use the newest version 0.6.0 and follow these directions

https://github.com/BitShares/bitshares/blob/bts/0.6.0/BUILD_UBUNTU.md

Wondering what you can do to help bitshares up to the 1.0 launch?

Toast has written a market maker bot for BTC/BitUSD on bter.com that Riverhead is now running (possibly others)

https://bter.com/trade/btc_bitusd

Volume is only 10 BTC so far, but notice the spread is around 5%. If you check out NuBits you can see that their spread is more or less the same: https://bter.com/trade/nbt_btc

This is most likely because the "trusted" custodians have lost shitloads of money by getting BTC dumped on them in the last crash, so they have widened their spread in an attempt to make money so they'll  stop being a fractional reserve. This is our moment to steal their market and surpass them as _the_ 1 USD token. All we have to do is to keep our spread lower, and then pump the volume! BTC isn't crashing any more so market making at a small spread will be profitable!

If you want to help BitUSD get adoption then get on bter now and start trading!!! Lets push the volume to at least 100 BTC as soon as possible!

Do you have a link to the market maker bot post?

Hi,

I set up a delegate delegate3.lafona and would appreciate any votes. I dont have enough DVS to vote in by myself but would very much like to be an active delegate. Thanks

I imported my KeyID json and used the wallet_collect_vested_balances command to try to claim my vested balance from DNS, however in the transaction history it is still listed as pending and doesn't show up as a balance in the account. Is there another step I am missing, or some time I have to wait? It was enabled at 25000, right?

Also I tried the command wallet_rescan_blockchain just to see if it would help.

Small typo in the second paragraph last sentence. "Recently Nxt added leased forging which allows one user do to delegate their forging power to another user." Is there a preferred way for suggesting changes?

Hi Bitty,
I believe you should receive BTS as part of the 11/05 sharedrop, as long as you owned them on November 5th. There was also a much earlier snapshot back in February I believe. One think you may want to check is to see if you have the most recent versions of the BTS client. I believe that v0.4.27.2 is the first to allow access to your vested balance from the 11/5 snapshot, but I still haven't tried it out myself. Hope this helps.

Quote from: delulo on December 17, 2014, 01:38:54 am

Quote from: svk on December 16, 2014, 09:50:00 pm

Quote from: delulo on December 16, 2014, 09:41:47 pm

I for example can not install / run .26 because

Quote

Large memory requirements during re-indexing and resyncing. At least 4GB RAM is recommended (swap file is not sufficient). Less RAM can cause freezing and crashes

since my client with my funds is on a vm with max. 2gb ram. source: https://github.com/BitShares/bitshares/releases/tag/v0.4.26
I didn't attempt to update it therefore.
If it is all easier and faster voting participation will also go up I think.

That wasn't actually true, you can re-index and sync just fine with 512mb RAM and a swap. Compiling is another matter though.

I have .24 atm. So the only way to update is compile newly right? So won't work?

You can always compile on another computer with sufficient RAM and then copy the executable to your VPS, that's what I do.

I have done the same thing with the chain to prevent issues with syncing and re indexing. Open updated client on computer with more RAM, let chain sync, close client, and copy over the chain folder. It takes a little while but seems to be working fine on VPS with 1 gb RAM.


I agree with the original post. It is currently very hard to get a new delegate voted in. With the number of feeds published, there should be plenty of room for good healthy competition. I'm excited to see how the new voting password helps.