I have some more good news, the Smartcoins Wallet will have full support for real Bitcoins, Dash and Steem soon (3 more chains). So, with just one mobile wallet, you will be able to hold the coins and assets from 4 different blockchains. I have a meeting on wednesday and thursday of next week about that to finalize who is doing which parts (it has to work with our new IPFS based BlockPay Core and BlockPay Engine). If all goes well, we will have that release of the wallet ready by Christmas.
 
Also, it looks as if we may be moving the BlockPay Core to C instead of Java, as this has helped us to port BlockPay Integrated to more hardware (such as the vending machines and gas pumps projects I mentioned earlier). The new Core and Engine should be ready for you by Christmas as well.

Bitshares needs to cater to forex traders and raise the fees.  Stop loss and take profit orders need to be implemented and the GUI for shorting smartcoins needs to be simplified.  Bitshares was designed as a dex, and every exchange makes its money through fees or spreads. Traders will happily pay these spreads for liquidity (which we don't have) and security (do have).
...
 A second worker proposal needs to be created for the implementation of stop loss and take profit orders.

 
A Worker to fund these things could work now with the anti-dilution guys probably attacking something else right now, but one problem here is the easiness of getting your Worker voted right back out again. Chronos has experienced this a few times, even our best core devs have as well. So we need a Worker to fix the Worker program, I think DataSecurityNode had some ideas on this topic.
 @BunkerChain Labs
 
Once that is fixed, then I totally agree, we need to be a bad ass Dex. Implement those Trader features you mentioned above.
 
Making the Shorting GUI a bit easier to understand as well. We just need mockups for that though. Take some screen captures, throw those images into a Paint program, draw the changes and then the Designer and Dev can get them implemented asap.

Cryptofresh is broken. Now it's not registering any activity or volume. What's going on? Can someone start a worker to create a new blockchain explorer?
I've been checking out the cryptofresh code on github to start doing it and downloading the graphene packages but I need help if I'm going to try to create a blockchain explorer.
@svk would it be possible to make a web page out of just the "explorer" part of the bitshares wallet? Maybe have some API calls that CMC could use to get the volume and price?
I don't know what it will take to get this fixed but I know that projects built on bitshares like blockpay need a solid blockchain explorer. @kenCode

PM me if you know how to get hold of @roadscape, if you want to start a worker to create a new blockchain explorer, or if you want to help me create one. I don't know how to program well but I can do python and I'd love to learn. Lets get going on this.

There is no need to create a whole new cryptofresh site.
If we can find a way to fund it (and i mentioned this today to btswolf) then Bitshares core development, new features, the web based block explorer and a slew of other things may need to be taken over by BitShares Munich for a short time. We would need enough money to pay for 2 years of hosting cryptofresh and the vps that will manage it (so no humans are required anymore). Getting worker proposals fixed (according to btswolf), adding the new dividends feature, these things must come first, so that if we have to do a fundraiser with a UIA for bitshares then at least we know those people who buy the token will get dividends on that purchase but right now there is no way for anyone to get a return really on investing in core dev for Bitshares.

Update on BlockPay IPFS integration...
 
Task-8: "File which handles the coin logos, coin name, details about the coin, etc."
Status: "Done"

Task-5: "File which handles sending/receiving loyalty points and UIA tokens"
Status: "In-progress"
 
Task-12: "File which handles all css or stylization standards, color codes, font weight and sizes, etc."
Status: "In-progress"

- We started fetching images from IPFS as we were storing logos as base64 encoded strings in our json files.
- Due to base64 encoded strings files became too large and IPFS daemon was unable to fetch.
- we decided to put logos as separate png files and their names in the corresponding json files.
- This approach reduced the file size as well as time taken by IPFS to download.
- We stored the image files in android as IPFS was sending the content of image file.

BlockPay - Day 2 of 4 at Oktoberfest and Bits & Pretzels events (some very sexy photos)
https://steemit.com/crypto-news/@kenCode/blockpay-day-2-of-4-at-oktoberfest-and-bits-and-pretzels-events
edit: a better link: http://steem.link/Rh3PC
 
Erik Voorhees (Shapeshift), @Chris4210 @kenCode and more:

BlockPay laying down on the job..

RE: Building IPFS and IPNS support directly into "BlockPay Libs" engine.
 
We are working on a proof of concept right now (to be done by friday of next week) where IPFS is fully integrated and completely decentralizes BlockPay as well so that it is unstoppable. "BlockPay API" will use this new Libs engine for integration with other apps, websites, etc.
 
BlockPay has been modularized in a way that allows us to use shared components across all versions of BlockPay across all kinds of systems and Integrations that we do (such as Odoo, SAP, ticket machines, etc etc). IPFS is now being added which further decentralizes BlockPay components and makes upgrades much faster over time and easier. If for example, App Stores decide to ban crypto apps or modules, or ISP’s decide to block “unapproved” crypto, IPFS has solved these problems as well since the files which run BlockPay and access to the BlockPay app will no longer require an App Store’s approval, http or even DNS.
 
Please find today's progress update below:
Task-1: "Create basic Android app for POC."
Status: "Done"

Task-2: "Implementation of IPNS/IPFS in Android app."
Status: "In-progress"

Task-21: "Research on development of non-http android IPFS library."
Status: "In-progress"

- We started researching IPFS libraries for android and found that almost all the libraries are using IPFS http api to get files.
- The libraries we investigated are: js-ipfs-api, go-ipfs, py-ipfs-api, js-ipfs, go-ipfs-api.
- We worked on somehow running IPFS daemon on android devices.
- We found a library that was doing something similar to it, however it was in kotlen language instead of java.
- We created a basic android app and tried to create IPFS daemon in it.
- We were able to create the daemon successfully, and are now working to grab the app files from it.
 
Next friday I will be ready to post more videos of the latest POC.
We are breaking new ground with IPFS here, this essentially makes BlockPay unstoppable and rock-solid, so when the tyrants start clamping down on crypto and crypto apps, BlockPay will still prevail.