cannot conected the pool

12:15:55

{
"blocks" : 8338,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00003799,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespermin" : "No information yet. Wait at least 4 minutes after starting mining for estimate.",
"networkhashps" : 857,
"pooledtx" : 0,
"testnet" : false
}


12:37:00

getmininginfo


12:37:00

{
"blocks" : 8345,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00003841,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespermin" : "No information yet. Wait at least 4 minutes after starting mining for estimate.",
"networkhashps" : 851,
"pooledtx" : 0,
"testnet" : false
}

block are going slower as the difficulty adjusts. But i think there is something wrong with the pool.

Thanks for the notice.  The pool was still finding the blocks and getting shares from people.  Just the website just was not reflecting this.  It has caught up once again and the shares were portioned out to the miners.  There is a job that runs every minute to update the statistics on the site and pay out but it stopped early in the morning.  This is the standard MPOS mechanism, we will have to tweak this a little to catch failures like this.

We are also looking into the connection failures.  Not sure what is going on with that yet though.  Every computer we try from connects fine so a little harder to troubleshoot without being able to replicate.

How come the pool only shows 1 active worker if I have 2 and am seeing them mine?

you may want to go ahead and remove openex from your exchange list. we will not be back for likely a very long time.

I had NoirSharesd running for over 24 hours.  I bought coins and transferred them successfully to the wallet.

I shut down the daemon.

I added gen=1 to the NoirShares.conf file to see if I could mine with the Daemon

This is the error:

NoirSharesd: kernel.cpp:368: unsigned int GetStakeModifierChecksum(const CBlockIndex*): Assertion `pindex->pprev || pindex->GetBlockHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)' failed.

Now I've set gen=0, and tried to start the daemon, and it's the same error.

I've rebuilt the daemon, and it's the same error.

I'm ready to delete the downloaded blockchain and see if that helps. This appears to be a problem with the NoirSharesd code though.

I'm trying this on Ubuntu, 32-bit


UPDATE:

This part is the most problematic it seems: double free or corruption (!prev)

What I did, was run it again, exported my private keys before the crash. I removed all references to gen=1 and gen=0 from my NoirShares.conf.  Created a completely new data directory, which generated a new wallet.  I imported the private keys again, and resynced the block chain.

My coins are back, and everything is good.

Word of warning, never put gen=1 or gen=0 in your conf file otherwise apparently you corrupt some of the data files or your wallet.

This is my findings anyway.

By the way, this miner:
https://github.com/reorder/momentum-getwork

..doesn't work for me. I can run it, but then it segmentation faults on me at this exact part of ptc.py:

hasher = PTSHasher(0, 0)

Segmentation fault (core dumped)


Can we not get a cgminer fork that has momentum algo in it?  Even if it comes off cgminer 2.x which had CPU capability in it?

Sorry to say we are still seeing issues with people trying to connect from the Asia region.  I am not sure what is blocking the communication.  For testing we bypassed any DDOS protection we had placed on the server to rule it out and one user has reported that using a VPN worked so it seems that something between the miners in that region and the server is blocking communication.  Still trying to figure it out because we do not have a good answer. 

That would be awesomesauce..

This would be great.  We are using the coyote miner created by bytemaster on bitsharestalk.org, https://github.com/InvictusInnovations/coyote_miner

This miner is not getwork based.  Unfortunately from looking at the source I do not think it is based on any existing protocol.  We did not modify the pool miner from that project, our only modifications were server side so the network protocol is the same. 

Having the client updated soon.

Please read the

Noir Investment Group

and

Investment Options

documents to understand what the next move is, now that we have established a stable network.

For now only the General Fund will be open. If you have any questions, please let me know.