BitShares is the only exchange that has order placing fees, which many people just cant get used to.

This makes it harder to run liquidity bots without paying loads on fees. Check out this buywall from an exchange that runs HFT bots: https://www.coinfloor.co.uk/exchange The buy wall is constantly changing every few seconds.

There was discussed previously a solution that will allow anyone to easily add liquidity:  bring back the proposed idea of feed relative orders. And allow choosing the feed for my order, so for example I can choose to use the BTS/BTC feed on the OPENBTC market.

Liquidity issues solved for all markets! I never understood the problem with this idea when it was proposed initially.

When keys are imported and claimed, their ownership goes to a new address which is derived from the wallet key (as I understand). So can those private keys be re-generated deterministically from the wallet key? Or after every address import do we have to make a new backup?

Thats what these docs seem to imply:

After importing your accounts and balances, we recommend to make a new backup of your wallet that will then contain access to your newly imported accounts and corresponding balances.

If thats the case then the docs should be more explicit. I wonder if this is where I messed up...

On the head of the bitshares branch of bitshares-2, Ubuntu 15.10:

make light_client

/home/me/source/bitshares-2/programs/light_client/Transaction.hpp:37:17: error: ISO C++ forbids declaration of ‘Q_ENUM’ with no type [-fpermissive]
    Q_ENUM(Status);

Does anyone have any ideas on that compile error?

Btw I couldnt find any documentation on building the light wallet anywhere. Its even not listed under in the Applications section in http://docs.bitshares.eu/apps/index.html

I know I can just compile the web wallet and use that as a light wallet, but Im paranoid and would prefer to segregate my private keys away from a general web browser that is used on a million other sites.

Version of Boost in 15.04 is 1.55, so that means bitshares-2 is not even compilable on the latest version of Ubuntu

Detected version of Boost is too old.  Requested version was 1.57 (or
  newer).

I guess Ill wait for a couple of weeks till 15.10 comes out.

Has anyone confirmed they will be running private feeds in 2.0?

Will there be private BitAssets for
-Altcoins?
-Stocks?
-Indexes?

Btw incentivizing good private BitAsset providers by paying them the transaction fees is genius. Economic incentives is where BitShares really stands out from the rest.

Private BitAssets: one entity publishes his price feeds into the blockchain without having to worry about paying a huge registration fee OR getting a median of 100 delegates - more efficient if you trust that entity.

Questions:
-Are they available from the release of 2.0?
-Has anyone confirmed they are going to be publishing private BitAssets for
--stocks? (Because the SEC will love it)
--Ethereum? (If you want to flirt with Ether do it here FFS)

On a related note I was watching Max Keiser the other day and he was talking about how his Box Office futures market was outlawed because the film industry didnt like it. He then mentioned decentralized prediction markets, and of course he mentioned Auger and not us. BitAssets for film box office revenue would stir a lot of attention. (Who wouldnt want to short an Adam Sandler movie?)

Here's an interesting idea Ive been pondering:

Large scale web applications typically have a web server that receives requests and does load balancing to the backend application servers. Requests are handled by as many backend servers as are needed to satisfy user demand.

There is the constant problem of how to sync up data across the servers, especially when one user's request can effect the validity/outcome of another user's request (such as an exchange website). So are there advantages to doing this using a private Graphene blockchain? Or does the extra redundancy of a blockchain make this inefficient relative to standard databases, with no real benefits?

It seems that running a p2p network as the backend of a website would be ideal in terms of taking servers down for maintenance, which is essential.

Nm I should have read the blog.