Quote from: dacoinminster on November 21, 2013, 11:30:00 PM

I think that everyone agrees we need to hire some of our developers full time. Tachikoma and I talked about this awhile back, and we realized that (like me) he was really expensive to hire full-time. However, the Mastercoin Foundation has a LOT more money now than it did then. I see no reason why we can't get at least two of our four devs into full-time positions. Ideally, I'd like to get all four. The payout from the upcoming bounty ought to make any transitions much less difficult for them.

+1000

I vote for 4 dedicated developers with a project manager or scrum master-like entity to get this organized into a focused effort and interface between the devs and yourself, while you focus your efforts on overall strategy and this is very important. Maybe you too should consider taking up a similar offer to work on this full time too?...This type of minimal business organization will definitely increase the efficiency of the full time staff several multitudes over. Also I think the main developers should get the awesome offers they are asking for...that is how you get awesome talent to leave and join new companies and we definitely want the best...what happens if tachikoma and others gets a promotion at his job with more responsibilities?

Quote from: rbdrbd on November 21, 2013, 06:41:18 PM

Great points. I'm no bitcoin expert obviously, but I know with bitcoin there are blockchain parsers (such as https://github.com/znort987/blockparser) that can run through and compile stats on the block chain (e.g. simple aggregate metrics, a list of addresses with balances and their balances, etc). Obviously, the rules behind mastercoin are a very good deal more complex than bitcoin, but perhaps some kind of parser could be written (not necessarily in C) that could run either as a one-shot (parse through the chain and output) or resident (with streaming output).

Output would be in a simplified JSON-formatted structure, that comprise "absolute actions" that have been validated through the spec-derived rule set encoded into the parser itself.

e.g "address A sent address B 50 MSC". In this case, the parser has done all of the difficult parsing and validation (such as, the sending address having the balance, the transaction being a valid Class A/B/C one, whatever else)...it outputs this in JSON format, a higher level web tool can either read it from a file (streamed or as a static/batch run) or maybe attach to the process's event interface via TCP/IP and get it that way.

other examples:
"address C put out an offer for 50 MSC @ .50/ea. offer ID is 1234".
"address D bid on offer 1234 for 20 of the 50 MSC"
"address E created a smart property named 'foobar' with currency ID 4567"

This way, all higher level utilities could hook into this Mastercoin daemon, which would take care of implementing the guts of the spec and take it out to a higher level streamed, JSON encoded "absolute" API, which would focus on things that have actually happened, after all of the parsing and rule validation have been taken into effect. The daemon could be available for windows, linux and mac OS X. A JSON RPC-driven query interface would also be available to allow querying of specific smart properties, transaction IDs, etc.

Hell, write the thing in ruby and use Tachikoma's work as a base for it. Or make it in python (everyone loves python, and that way I'll want to hack on it! :p)

....We shall call it.... "mastercoind" (*pinkie over mouth*)

Maybe I am smoking crack here and this won't gain us much. Just thought I'd put it out there to get the ball rolling for potential solutions. If doing the above makes sense, it would bring us in line with the way bitcoin does things (e.g. bitcoind hooking into exchange sites, armory client, p2pool, pushpool daemon, bitcoin-qt, etc), and speed new development efforts up 20x, as what we're doing now seems a bit similar to forcing everyone who wants to build their own computer to create the CPU from scratch, instead of just buying the parts and slapping them together.

I agree with you rbdrdb, even though I am formally trained with c++ I generally avoid any headaches from tinkering with lower level engineering. We DEFINITELY NEED a "Master Daemon", your recommendation is needed and I don't think that it should be treated as an after thought , rather to have a small number of developers working along side main devs on the "Master Daemon" which opens up the platform to everyone just like bitcoin https://en.bitcoin.it/wiki/API_reference_(JSON-RPC).