Clearly someone is abusing the fact that the banning feature of my pool isn't working properly...
Not clear enough mate. Why isn't banning not working? This is a core feature of NOMP and if it has a bug, it should be reported to the dev. Can the pool determine if the connected miner is a legit one or not? I'm sure the problem is not the banning functionality (EDIT: unless of course this is a configuration issue). Also, what is the above statement supposed to mean? That anyone can leech coins because banning does not work? Be more clear please. Are you running custom shinycoind and NOMP code? It's a bug in node-stratum-pool: https://github.com/zone117x/node-stratum-pool/blob/master/lib/stratum.js#L405options.banning.time should be multiplied by 1000 https://github.com/zone117x/node-stratum-pool/issues/90 |
|
|
|
Clearly someone is abusing the fact that the banning feature of my pool isn't working properly...
Not clear enough mate. Why isn't banning not working? This is a core feature of NOMP and if it has a bug, it should be reported to the dev. Can the pool determine if the connected miner is a legit one or not? I'm sure the problem is not the banning functionality. Also, what is the above statement supposed to mean? That anyone can leech coins because banning does not work? Be more clear please. Are you running custom shinycoind and NOMP code? I don't have time to explain now, looking into the issues. Are you running custom shinycoind and NOMP code? Yes & yes All I can say now is that if you try to mine with unsupported software, you are wasting your time. |
|
|
|
|
Clearly someone is abusing the fact that the banning feature of my pool isn't working properly...
|
|
|
|
Is it normal not to find a share in well over 30 minutes ??
...
EDIT : The same on another server!
...
Maybe vardiff is not a good idea ??
You should be getting 1 share every 3 minutes on all your machines combined, does not matter which IP. It's worker based Vardiff |
|
|
|
Seems like i cant build on ubuntu 12. Anyone has build command? I'm using sudo apt-get update && sudo apt-get install libcurl4-openssl-dev libjansson4 autoconf git make && git clone https://github.com/siklon/shinyminer && cd shinyminer && ./autogen.sh && ./configure CFLAGS="-O3" && make && make install What error do you get? Try also installing automake and gcc This error ramhog.c:38:102: error: ‘MADV_DONTDUMP’ undeclared (first use in this function)
Fixed that, it will know also let you know when Hugepages are enabled, so you will know when to expect a performance boost. Personally I got a 27% boost by enabling Hugepages (from 22 HPM to 28 HPM). |
|
|
|
I am getting too many of these :
[2014-07-07 11:50:22] stratum_recv_line failed
[2014-07-07 11:50:22] Stratum connection interrupted
[2014-07-07 11:50:25] thread 0: 7 hashes, 15.66 hash/m
[2014-07-07 11:50:25] thread 1: 7 hashes, 15.65 hash/m
[2014-07-07 11:52:24] Stratum connection timed out
[2014-07-07 11:52:24] Stratum connection interrupted
2014-07-07 12:09:35] stratum_recv_line failed
[2014-07-07 12:09:35] Stratum connection interrupted
[2014-07-07 12:10:21] Stratum requested work restart
Is my hash is being wasted here ?? I am getting stratum_recv_line failed and Stratum connection interrupted every couple of minutes
Turn on -D -P to see if your shares are being processed when they are submitted. |
|
|
|
Hello, I got this when attempted to compile the miner: ramhog.c:38:102: error: ‘MADV_DONTDUMP’ undeclared (first use in this function)
madvise(pool->scratchpads[i][j], pool->C * sizeof(uint64_t), MADV_RANDOM | MADV_DOFORK | MADV_DONTDUMP | MADV_HUGEPAGE); Any idea? Funny macro's names: DOFORK, DONTDUMP  Edit: Answering myself. That are madvice functions MADV_DONTDUMP works since Linux 3.4 and I have 3.2 kernel.Edit2: Kernel upgrade didn't help  LMAO about the macro names!  So, there is absolutely no chance it can work on centos 6 with the stock kernel 2.6. (@primer) Yea these macros aren't really needed, you can remove 'DOFORK, DONTDUMP'. |
|
|
|
Shinyminer performance is increased by 25-30%. https://github.com/siklon/shinyminerUse following CFLAGS : "-Ofast -funroll-all-loops -march=native" IMPORTANT - Set hugepages: "sysctl -w vm.nr_hugepages=7680*<RAMHOG_THREADS>" ramhog.c: In function ‘ramhog_thread_pool’: ramhog.c:38:118: error: ‘MADV_HUGEPAGE’ undeclared (first use in this function) ramhog.c:38:118: note: each undeclared identifier is reported only once for each function it appears in What are you compiling on? Ubuntu 13.10 works |
|
|
|
Shinyminer performance is increased by 25-30%. https://github.com/siklon/shinyminerUse following CFLAGS : "-Ofast -funroll-all-loops -march=native" IMPORTANT - Set hugepages: "sysctl -w vm.nr_hugepages=7680*<RAMHOG_THREADS>" |
|
|
|
I'm in the final stages of testing the wallet RAM fix. It will be a non-forking change, but I encourage everybody to update their nodes as soon as possible. The github will be updated in a few hours.
The solution I found is to assign a hash-signing private key. The node who owns this key verifies that the ramhog hash for a particular block is accurate, and then signs it. Any node that trusts that key uses the signed hash instead of computing it itself. All nodes propagate these signed hashes so that they are easily accessible. The result will be that anybody can run a wallet without needing to run the ramhog algorithm. This will also make sync times near-instant. For the security of the network, I suggest that those who have the RAM not use the signed hashes, or perhaps only use them to sync and then let their wallet verify all the hashes itself.
I will also hard-coded the genesis block info and the seed nodes in the OP and set the default to not run any ramhogthreads, so the average user can just download and run the binary without needing a special computer. These nodes still fully validate all transactions as usual. The only difference is they don't compute the proof-of-work hash themselves.
Laxori666, instacash, could you please recompile the Windows and Mac wallets once the source is posted?
Awesome work. So only if ramhogthreads=0, it will use the signed hashes? |
|
|
|
Dev What time to burn coin pool ？ Burn coin pool will let the coins shine！
This is something that I'm working on.  |
|
|
|
SHC pool When sent to the miners' wallets, delay a long time?
280 confirmations needed. Takes many hours. @7000years, seem you and primer- are both bag-holder of this coin, right?, i read though all pages and see you guys are willing to sell a thousand  Actually, I am a small bag holder. Hash power too expensive! Primer is the rich guy! I mean, just look at his sell ads! But there is also another miner with an army of boxes on amazon! BTW, I haven't posted a sell ad anywhere... I may be rich but am sure not getting any richer with shiny. I will be switching all hash power to XMR today, dev is incompetent, very unlikely the coin is priced well when/if it hits an exchange. EDIT : If anyone is looking for cheap shn, i'd be willing to sell half of my holdings, 10,000 SHN for 1 btc. Got bills to pay.. the total amount of shiny is about 21mil (right?). So 10,000 SHN for 1BTC is unreasonable (meaning Shiny's market cap is 2100 btc?). I can offer you 0.1 btc for 10,000SHN. PM me if you accept. No one will be selling for that low unless they don't mind mining for a loss. |
|
|
|
C'mon people, point your miners to the pool! Better for everyone.
I've pointed my hash to Sandor's pool, and I encourage everyone to do the same. It's been quite a while without any valid block. I wonder if all issues have been resolved with the pool. Block found. |
|
|
|
|
More hashes are needed to find a block, the diff is really high.
|
|
|
|
The pool wallet has 0 connections... it got banned from network, not sure? I am looking into it.
Does anyone have some nodes I can connect to? addnode=144.76.139.178 addnode=144.76.139.103 addnode=144.76.139.104 addnode=144.76.139.105 addnode=144.76.139.106 addnode=144.76.139.107 addnode=144.76.139.108 addnode=144.76.139.109 addnode=144.76.139.110 addnode=144.76.139.111 addnode=144.76.238.233 addnode=144.76.238.235 addnode=144.76.238.236 addnode=144.76.238.237 addnode=144.76.238.239 addnode=144.76.238.242 addnode=144.76.238.243 addnode=144.76.238.244 addnode=144.76.238.245 addnode=144.76.238.195 Perfect, syncing now. Thanks It appears the pool did get banned from the network, no clue as to why though. Looks like it will take an eternity to sync back up again, 27 hours if my calculation is right? 27 hours if syncing from block 0 30 minutes if syncing from 48h ago. Broken coin Whoops, actually was 3 hours from block 0, heheh... |
|
|
|
The pool wallet has 0 connections... it got banned from network, not sure? I am looking into it.
Does anyone have some nodes I can connect to? addnode=144.76.139.178 addnode=144.76.139.103 addnode=144.76.139.104 addnode=144.76.139.105 addnode=144.76.139.106 addnode=144.76.139.107 addnode=144.76.139.108 addnode=144.76.139.109 addnode=144.76.139.110 addnode=144.76.139.111 addnode=144.76.238.233 addnode=144.76.238.235 addnode=144.76.238.236 addnode=144.76.238.237 addnode=144.76.238.239 addnode=144.76.238.242 addnode=144.76.238.243 addnode=144.76.238.244 addnode=144.76.238.245 addnode=144.76.238.195 Perfect, syncing now. Thanks It appears the pool did get banned from the network, no clue as to why though. Looks like it will take an eternity to sync back up again, 27 hours if my calculation is right? |
|
|
|
The pool wallet has 0 connections... it got banned from network, not sure? I am looking into it.
Does anyone have some nodes I can connect to? |
|
|
|
|
The pool wallet has 0 connections... it got banned from network, not sure? I am looking into it.
|
|
|
|
|
Show Posts
