I'm liking the development schedule you have laid out so far, seems very well thought out. Is there any concrete planning done yet on exactly how the system will be modular? What I mean is, for instance, if a part of the autoexchange engine doesn't quite fit what I need, but I have my own program that can pass commands and arguments through it via cli or even http, is that possible? Its understandable if you're not quite ready to elaborate on that for whatever reason but would love any explanation you're able to provide. At the moment I'm mostly running a solo venture as far as my pool stuff goes and CoiniumServ has definitely been looking attractive since the finished product is meant to be fully featured and flexible, allowing me to offer excellent services without having a huge staff, or budget. The ability to plug in some of my own tools (without having to resort to reverse engineering or hacking anything) would make it even more attractive, though I could be assuming too much, too early. Still, watching eagerly. Just wish I had more time to test!
The plan is that we won't be releasing a ready-to-work auto-exchange code with - the number #1 reason is that auto-exchange pools as you know dumps coins and for the most part makes the coin prices to drop. But we have a plan for that which is quite different then nomp;
We'll create an auto-exchange module API that CoiniumServ can consume, so basically to get started with a new exchange-service working, you just need to put a simple module for CoiniumServ and fill in the details about connection to exchange-api. Then you'll be able to fill the exchange logic - which will allow you to code your own unique exchange logic;
The api is not here yet but will be something similar to this;
var txId = your_exchange_module.Send(dogecoins)
await your_exchange_module.Sell(txId)
var newtxId = your_exchange_module.Get(bitcoins-for-txId)
-- payment processor will do the rest to distribute the bitcoins for miners who contributed dogecoin mining period --
So we'll have two options
1) Use the above exchange module API and code your own simple exchange module so coiniumserv consume it's services (which is already what you are looking for).
2) For our own pools
coinium.org, we'll develop our own proprietary exchange modules for our in house use, but will still have paid consulting services for people whom can't afford developing the module themself. Consulting services we allow the development of the software to continue on.
Edit: Had another go at building it but not having any luck yet. I've barely even gotten my feet wet with C# or Mono so it is possible I'm just missing something or not set up quite right yet. I did get those repos added and installed mono-complete and mono-opt along with its extra dependencies.
With a bit of googling I'm thinking it is something on my end that I just need to wrap my head around a bit more. Once again, though, I've worked the night away and the kids will be up in a couple of hours, so I'll try again tomorrow. Following is a snippet of one of the errors I was getting when running the build script.
Utils/Logging.cs(97,43): error CS0012: The type `System.Object' is defined in an assembly that is not referenced. Consider adding a reference to assembly `System.Runtime, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
Will be lot better if you can paste a full build-log to pastie.org so I can check it out.
and maybe also give this command a try;
