Topic: CoiniumServ - open source & high performance pooled mining server software - page 20. (Read 105777 times)

Wow, nice project!

Is there any chance to have primecoin algorithm too? ;-)

Any chance a dev will be on IRC anytime soon?  For the life of me I cant seem to get around unable to sign block, wallet locked? for tekcoin.  No the wallet is not locked, running as daemon on linux and never encrypted.

v0.1.2 alpha is here with a major payments bug being fixed; https://github.com/CoiniumServ/CoiniumServ/releases

v0.1.1 alpha is here! https://github.com/CoiniumServ/CoiniumServ/releases/tag/v0.1.1-alpha

we are too close to milestone1, expect an alpha for testing soon guys! https://github.com/CoiniumServ/CoiniumServ/issues?milestone=1&state=open

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;


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;

Oh wow, that video reminds me of when I was folding for a bit a while back. Nice!

I haven't had any free time lately to test it out, I had started to a couple of weeks back and was having some issues and haven't had time since. Running several pools and keeping up the backends, maintaining a few small projects as well as helping with a friend's setup, tiring..

I'm pulling the repo now and will give it a look before turning in tonight. Very excited about it, as the goals of this project fit with my overall aims, and I'm hoping that its modular nature will allow for me to use some of my own customized backend tools.

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!

If you wish, feel free to PM me.

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'

CoiniumServ source code visualization

http://www.youtube.com/watch?v=6qHMiNbfH7s

Right now it does support scrypt (and will add sha256 coin support soon - like BTC), x11, x13 and similar algo support will also eventually added.

Thanks for your interest on the project.


We will be soon releasing a feature-complete alpha version for testing stuff and so. The next step will be a feature-freeze where we'll be fixing the bugs in basic functionality. Next in the line we'll implement multi-pool capabilities. Check our list of milestones here; https://github.com/CoiniumServ/CoiniumServ/issues/milestones

So basically for switching and autoexchange we need to first make sure that the basic functionality is all tested & working as intended.


Coinium.org pool website is proprietary frontend, but CoiniumServ project will feature a similar one which you'll be able to customize for your needs easily.

@jmax, can you handle your debug.log please?

For some reason I can not run more than one miner on one instance of cgminer using this pool. Are there any fixes for this?

for litecoin-testnet i use a this config;


You should be having something similar to this, if the problem persist can you paste your litecoin.conf please?

Well I did not know that the coin daemon is a separate process.
So I have the litecoind running now and it looks like I am past the issue with communicating to it...
However, now I have the same issue as the previous person.
I am getting this exception:  throw new Exception("An unknown web exception occured while trying to read the JSON response.", webException);
I am running on windows dotnet.

Any help on that one?

Thanks!

Nice video.
I see you were using the dotnet version.
I have mine running but I do not see many of the printouts to the console that we in the video init the pool etc. (my version is a couple a days newer that then one in the video - I think.
When mine runs - it gets a timeout exception trying to communicate with the coin daemon.
the config file has the daemon address as 127.0.0.1 port 9333.
Are those settings accurate?
I do not see any process listening on port 9333 - which may explain why the request is timing out.

Any ideas?

06/29/2014 15:48:19 -04:00 [Information] [global] [n/a] CoiniumServ "0.1.5293.24129" warming-up..
06/29/2014 15:48:19 -04:00 [Information] [global] [n/a] Running over DotNet 4.0.30319.17929.
06/29/2014 15:48:20 -04:00 [Debug] [Pool] [n/a] Generated cryptographically random instance Id: 974328085
06/29/2014 15:48:26 -04:00 [Information] [Redis] [n/a] Storage initialized: "InterNetwork/127.0.0.1:6379"
06/29/2014 15:48:27 -04:00 [Information] [PoolManager] [n/a] Discovered a total of 1 enabled pool configurations: ["Litecoin"].
06/29/2014 15:48:27 -04:00 [Information] [StratumServer] [n/a] Stratum server listening on "0.0.0.0":3333
06/29/2014 15:48:27 -04:00 [Information] [HttpServer] [n/a] Vanilla server listening on port 3334.
06/29/2014 15:48:27 -04:00 [Verbose] [DaemonBase] [n/a] Send: "{
    'method' : 'getblocktemplate',
    'params' : [
        {
            'capabilities' : [
                'coinbasetxn',
                'workid',
                'coinbase/append'
            ]
        }
    ],
    'id' : 0
}"


then it hits:   throw new Exception("There was a problem communicating with coin daemon.", exception);

Thanks!

Solo mining with CoiniumServ & Windows

http://www.youtube.com/watch?v=z6h4-4tdxvI

DRKLord, we'll be soon posting a detailed documentation & usage guide soon. The develop branch code is still being worked and not yet production ready, but the good news is that, startum-server code's initial implementation is done now.

here's a few screenshots;

running over mono & ubuntu:


running over dotnet & windows


the first litecoin-testnet block found by coiniumserv: https://chain.so/tx/LTCTEST/5d3b79637855994ad582b1c304ea29525f1f644fa4fcc48f69954558768a30fe
and even more testnet blocks: https://chain.so/address/LTCTEST/n3Mvrshbf4fMoHzWZkDVbhhx4BLZCcU9oY

@drklord and please try this;

git submodule init
git submodule update
cd build
./build-mono.sh
cd ..
cd /bin/Debug
./CoiniumServ.exe

And give it a try, you'll have a debug.log file in bin/Debug/logs and it'll be very helpful for me to identify the problem. And keep in mind that right now scrypt is hardcoded for time being (will support sha256 coins soon too)

First of all, I want to give this project my highest praises! Well done! This is EXACTLY the sort of mining pool software I've been looking for, and I LOVE C#/.NET/Mono!!!

However, I'm having a few problems with the code...

After I downloaded the .zip of the repo, I noticed that the project's dependencies were missing. It was missing Gibbed.IO and Json.RPC / AustinHarris.Json.RPC... I then downloaded those dependencies from the master branch and made a few modifications and reloaded them. I got the code to build and run in DEBUG config successfully. But I'm not able to tell if it's actually communicating with bitcoind... And when I try to connect one of my AntMiner S-1s, it throws an exception in the GetJsonResponse(HttpWebRequest) method of the DaemonBase class...


^ I haven't yet been able to determine what's going on here or what the problem is. I just downloaded the code today, so I haven't had much time to dig in and explore it. But if anyone can help me figure out what the problem is and why this exception is being thrown I would greatly appreciate it!!! 

Also, I'm having trouble figuring out whether or not the pool software is successfully connecting to my *coind server and getting valid getwork responses. Does anyone have an example config file or some tips to help me out here?

I'm REALLY excited about this code/project and very eager to get it up and running. If anyone can help me out here I may have a bit of extra coin I can send your way... 

Thanks!

The DRK Lord

master-plan: https://github.com/CoiniumServ/CoiniumServ/wiki/Master-Plan

Cgminer accepting jobs & sending notifications;