• create a forum.invictus.io subdomain parked on or redirected from bitsharestalk.org
• submit content to this wiki page (and/or other DAC related) http://en.wikipedia.org/wiki/Smart_property with a link back to I3
• submit comments to this article (and/or other DAC related) with a link back to I3  http://www.forbes.com/sites/jasperhamill/2013/11/30/fed-up-with-bitcoin-heres-how-to-start-your-own-currency/
• All I3 stakeholders consider incluing a link back to I3 in your profile signature on https://bitcointalk.org/
• subscribe/deploy an Alexa Pro SEO plan http://www.alexa.com/pro/advanced?ax_atid=b4040b60-6210-4eba-8f6e-afdb6edc8546

Invictus is working closely with Bithaus to build an open source wallet / block explorer for BTS X....

We would like this library to be useful for all our various chains, especially BitShares Music which Cob has taken the initiative to bootstrap with our help.

As far as appealing to smart people to join the team....  we have senior engineers from google contacting us for jobs and several people who are working with us or to whom we have extended offers also have offers on the table from google.   Unfortunately, in addition to finding people with the proper skills there is also a need to find people interested in taking the risks and who are on the market at this exact moment.     We have extended offers to an individual who found the majority of major security bugs in Bitcoin with years of experience.

The problem we have is that anyone with the skills to develop blockchain technology without months of training is already doing so (one of the alt coins) and their own pet projects are more interesting to them than even a highly paid position working for us.   Often they have prior commitments (school, job, kids, etc) that mean from the time we convince them to work with us that until they can start work is at least a couple of weeks if not a month or more.   

It is not unusual for a company looking for programing talent to take months if not over a year to fill a few positions.

Quote from: toast on March 07, 2014, 04:17:02 am

Positive time!

I think the last iteration swag doesn't appeal to the types of people you would find at bitcoin conferences. In a recent conversation, another forumite gave these characteristics:

Quote

-95%+ predominantly male
-higher education than average
-at the very least they already know about bitcoin and probably have general idea of the implications of blockchain technologies and decentralized systems
-have philosophical and political views that align more with libertarian and anarchist perspectives
-more than likely have a monetary incentive; or some variation of self-interest

My opinion is that you need a clean, simple t-shirt design with a company or product logo and your favorite from among these:

* Decentralize Everything
* Decentralized Solutions to Centralized Problems
* BitShares X: Decentralized Bank and Exchange
* BitShares ___: _______
* Life, Liberty, Property
* Reimagine Everything, with some visual aid to tell you what kind of things to reimagine

Thanks!  Now THAT's what constitutes a constructive comment!

 

Hi, I wish you a really awesome time at the conference. You are doing a great job. You communicate good, are polite and your interview on the radio I heard yesterday, Sovryn Tech, was excellent. Toast went mental

Enough is enough.
https://fbcdn-sphotos-c-a.akamaihd.net/hphotos-ak-prn1/t1/p180x540/1926683_10100144247329332_66264429_n.jpg

http://dacindex.com

Part one of this two part project is out in minimum-viable-product form.   Tracks all 2.0 metacoins right now using CoinMarketCap data, we're moving towards custom metrics and figuring our the best way to determine an index price.  I'm thinking it might be market cap / 1,000,000 BUT with coins like XRP and NXT in there you can't really do anything by market cap because their volume is soooooooooooo low relative since most of the coins are held in few hands and don't trade.

So Protoshares is doing well because we're doing the primary ranking by 24hr market volume, which is a more real estimation of whats going on.

Comments are welcome but just be aware this is a very early project and a proof of concept launch.

Quote from: sschechter on March 04, 2014, 03:44:59 pm

I write Java code for a living, and quite frankly, I have not seen anything more demoralizing than trying to build the Bitshares/Keyhotee workspace.  I have wasted countless hours on this to no avail.  Every hurdle cleared is met by the next obstacle.  If it were not for the fact that I have a DAC I want to build, I would have given up long ago.  I have invested far too much of my time and money for me to let this die.   THIS IS A CRITICAL ROADBLOCK FOR ANY POTENTIAL DAC DEVELOPER! For better or worse, my target platform is VS2012/Win7/64.  That means in addition to building the workspace on my platform, I need to build every single dependency on my platform too.  Quite frankly, the documentation to do this sucks.  The error codes suck.  The support sucks.  Not just I3,  but Boost, Qt, etc, everyone who needs to support my platform.  It sucks because every platform has its own set of quirks that the user must be familiar with,  and if every user is using a different environment, it increases the chances that they get unique errors that no one else has seen before.  Why did I pick my platform?  Because no one told me "use this" instead.  I would much prefer something that I know works than something I have a base level of comfort working in.  I was not married to using VS2102, but I may just be now since I've spent so much time on it. If it weren't for sites like Stack Overflow, I would be nowhere.  This is not just my problem.  This is everyone in the community's problem.  If I can't build you a DAC, then you are getting cheated as an AGS/PTS holder.  Like I said, I write Java code for a living.  I figured there would be some bumps along the way getting re-acquainted with C++, but this is just unacceptable. If I do this for a living and can't get this working, then I can't be the only one whose had issues and given up.  I'm willing to bet that there are others who have been made to feel stupid by this opaque process, and that they've been made to think that these issues are due to their own technical limitations. 

Here is what I propose as a solution.  I3 needs to hire a full time configuration management specialist.  They should be responsible for all working build environments.  Having a bounty for a working build system is not enough.  This CM person would be responsible for maintaining at the minimum, one working Windows, Mac, and Linux environment.  They would need to write tutorials for building the workspace for developers.  This has to be a step by step guide for building every dependency from a clean machine.  Make no assumptions about what the user knows.  I want a complete list of tools to use and the URL to find them.  It should be written in such a way that a non-developer can set set up the workspace.  And finally, they should be supporting developers who are still having issues in order to get it working.

ps - When building Qt statically, I get the following error, so please try to convince me that this doesn't suck:

NMAKE : fatal error U1077: 'cd' : return code '0x2'

 
It's been a disaster, I abandoned trying to build as well

They are working on an automated build system but it couldn't come fast enough.