[ANN] NoirShares Trade on PoloniEX, Noir Investment Options Open

[Hollowman338]

OpenEX is shutting down. 

[1714814770]

1714814770

[eddywise]

cannot conected the pool

[MiningViking]

Time Since Last Block   3 hours 50 minutes 20 seconds

with more then 2/3 of the network on the pool!?

[barwizi]

Time Since Last Block   3 hours 50 minutes 20 seconds

with more then 2/3 of the network on 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.

[MiningViking]

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

Well pool seems to be finding blocks again, it might just been extremely unlucky and i mean waiting for the bus and get a Boeing 737 in the head kind of unlucky.

Nice to see NRS get some love at Poloniex, trade volume up almost x10 since yesterday

[pinwc4]

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.

[miningcrew]

I know it is peanuts but im willing to donate 0.1BTC to whoever puts up a working pool for NRS.

Now there is a pool... - network hashrate increased from 85 to 1000+ within 24 hours.

But immediately there are miners, who are prepared to sell coins at costs (+10%, 20 %), if I look at prices at Poloniex

There will not be many NRS and the reward (per block) is decreasing quickly - why some people sell at such low prices (volume is pretty high)?

[criptonauta]

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

[barwizi]

Are you planning to repair Noirbits?

My client syncs correctly meaning (hopefully) the chain is functional, however, once i get time i am either updating it to the latest litecoin-codebase or moving it to an altogether new algorithm. noirbits.com is offline, NoirBits information will be uploaded to the Noir Investment Group website, along with other important info like pools.

[r3wt]

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

[pinwc4]

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

Did you create 2 separate workers?   If you point all your clients to one worker name the pool will only display it as one worker. 

[toldy]

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

Code:

*** glibc detected *** NoirSharesd: double free or corruption (!prev): 0x099eb758 ***
======= Backtrace: =========
/lib/i386-linux-gnu/libc.so.6(+0x75ee2)[0xb7051ee2]
/usr/lib/i386-linux-gnu/libstdc++.so.6(_ZdlPv+0x1f)[0xb727a51f]
NoirSharesd[0x80e3093]
NoirSharesd[0x80e316a]
/usr/lib/libboost_thread.so.1.48.0(+0xb1cc)[0xb76931cc]
/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb72bcd4c]
/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb70cbbae]
======= Memory map: ========

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?

[pvkpgp]

The pool   can't connect

attempting to connect to nrs.blockquarry.com
3197931ms th_b       miner.cpp:106                 main                 ] 107.16
1.23.73:4444
3219023ms th_b       miner.cpp:112                 main                 ] unspec
ified
由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。
    {"message":"由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试
失败。"}

[pinwc4]

The pool   can't connect

attempting to connect to nrs.blockquarry.com
3197931ms th_b       miner.cpp:106                 main                 ] 107.16
1.23.73:4444
3219023ms th_b       miner.cpp:112                 main                 ] unspec
ified
由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。
    {"message":"由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试
失败。"}

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. 

[yvg1900]

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. 

Is your pool using getwork? I may add support for your pool in upcoming yam release.

yvg1900

[MiningViking]

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. 

Is your pool using getwork? I may add support for your pool in upcoming yam release.

yvg1900

That would be awesomesauce..

[lumeire]

This one's more profitable to mine than MMC imo. 

[pinwc4]

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. 

Is your pool using getwork? I may add support for your pool in upcoming yam release.

yvg1900

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. 

[pocketbits]

bump! please support my wallet! 9qAvA2wD58tCfsZF8Es2JPYwQQsA8Wiwe4

i can't mine or install wallet until I get home from work in 9 hours!

[barwizi]

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.