If there is two miners already, they should be added to the OP.
Do we expect every person to sift through 70+ pages to find them?
On that note, can someone link me to a windows binary?
It's obvious without pools we won't be getting any blocks. The cloud/botnet miners have obviously jumped on.
Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 143. (Read 284956 times)
June 05, 2014, 12:32:29 PM
June 05, 2014, 12:18:45 PM
30 blocks found by the pool, any chance we get an estimation on how much we are to make from immature blocks ?
Not currently, but I am working on it.
June 05, 2014, 12:13:40 PM
30 blocks found by the pool, any chance we get an estimation on how much we are to make from immature blocks ?
June 05, 2014, 11:16:56 AM
I tried to use minerd -dcrypt on the pool and I only get rejected...
you don't need to supply the algo when using slimminer, dcrypt is the default algo. however, the correct cmd line would be:
Code:
minerd -a dcrypt -o SERVER:PORT -u USER -p PASS
anyway
I am placing a new bounty of 0.15BTC (!!!!!!!!) if someone adds the rpcthreads function to git and it gets accepted by the dev. Deadline : 24h
I can confirm that he pays the bounties he offers.
Recompiled with the modification and now I am getting shares
June 05, 2014, 10:53:45 AM
Apparently there are 4 kicked blocks, which means that the daemon could not find the transaction for it at that moment, however currently these are valid blocks and I will add them back to the unconfirmed.
Kicked blocks, that sounds reassuring. Who kicked them and why
How come the daemon did not rescan the transactions on the next update ? You are good at finding orphans but not as good at detecting all good blocksOnce the daemon doesn't find the corresponding transaction, the blocks are kicked forever by the pool, https://github.com/zone117x/node-open-mining-portal/blob/master/libs/paymentProcessor.js#L222
IMHO It would be better to let the daemon retry atleast 5 times in period of 5 mins before kicking the block, let me see if I can change it and propose them to merge the fix.
I never had kicked blocks before, so I guess the buggy wallet is to blame.
June 05, 2014, 10:47:43 AM
Apparently there are 4 kicked blocks, which means that the daemon could not find the transaction for it at that moment, however currently these are valid blocks and I will add them back to the unconfirmed.
Kicked blocks, that sounds reassuring. Who kicked them and why
How come the daemon did not rescan the transactions on the next update ? You are good at finding orphans but not as good at detecting all good blocks June 05, 2014, 10:37:00 AM
POOL STATS
slimcoin dcrypt 58 499635 25702 105 12 0 89 596.92 KH
Sandor111, the stats are not in real time are they ? There are more workers than 58.
Please confirm if only 12 blocks have been mined so far
slimcoin dcrypt 58 499635 25702 105 12 0 89 596.92 KH
Sandor111, the stats are not in real time are they ? There are more workers than 58.
Please confirm if only 12 blocks have been mined so far
Actually 16 blocks. 89 blocks are orphans because the pool was in the wrong fork 10 hours ago. After that sandor111 said everything works fine. But I don't understand why the pending blocks decrease but the confirm blocks doesn't increase. Ok it doesn't get confirm yet but where does it go ? Something wrong with the stats.
Apparently there are 4 kicked blocks, which means that the daemon could not find the transaction for it at that moment, however currently these are valid blocks and I will add them back to the unconfirmed.
The other blocks found:
[blockHash] [txHash] [height]
Code:
0000000740bb234239788af32a835f847574503d2c59d6b74073804358c49d8c:9063f772114ac38674d4455a27993fc27e6de70d1fd27e18f4f1d3f3ac0ca6e0:6939
00000004d4c61ea956f4798310f35150ae8f407042dc7c1f16b3169a70add760:4a6c0d528a3e82af14cd0db5e10bdd15abbbaed169562b42ee415084e7a02659:6937
000000061bd812a903e6ad00d2bd9582606afd8f9c87b0d53c3e37e023d3c728:b95998352eb035fbdc40cec64e5ad085a9045bbb3b4379b46a2e54da6909e7dc:6882
000000007fe04e9bbdef378b59059828c69672b0ab956072c29f3aaea83b6bd3:77f910820f23c282687316b516f3bb5216eaf5b6c19eba1b6ca97987059ac97d:7002
00000003360b6638fa2be832f2b7dbd0ee24867d52d8574ca55b06e442e483bc:2d18aea4e9ff3c096d4eadc30f6ce2e0a39caef838885299e811a9157d64339b:6993
000000025af4a288f83efb1c04208d02343748f8aea1a3e783cf42b83183f5a2:84aed640746ce1e943406c581733088c18096955f679fc11ff7d45127307074c:6983
000000094e1b6cc3c4a61279ebfebabba56fcad98a2315575597dd722c9b1c1a:5e726f0f36171bdb0ef1c3020f9b04ee67eeb010746304c0d463f26ca6bb1e53:6816
0000000493cebe4dcf2be960ccac21fadf666617103b0950de35560afe1816bb:ed259564a0d39c657be1f5578b2761218ea080346f26ffa520966567b0992c85:6664
00000000506207a5fb17c75527480dce2369ec638cccdef81fd1e11a0ce7678f:e1f7623114cff22a6600b83c1ef7f2b69e829f691d7e9d3f0405127e5b5a11f6:6877
00000008deac63b99a80a20d364450fd1a64021996fb044e6fb218be5e0859dd:6c068a414253beb512e3a2db1b908a61bb5fa880e7e2f873d6f258295bf2dc1f:7000
0000000a0e27e1567cc5e5270d83a0f0cbf7d752d88901644d30e1babb4c4c98:6abbd7e9c92ddc13c623c1ecd82e9c263f1a8576e33551deba8c25257b06d72f:6749
00000004d4b493a1336b2cb394043f5ff04eb19c53dfa77ff0f0c80b726b75bd:146284ebec31f9bf4d396a949b767102f46b074bd69d4e485bb00f474b68bcee:6880
0000000795a2e5ee0f352fe6d49efe5b03e8b694d64aa48bad14cb6d4bf7c18b:64adfef765b1740474c159afd625c3f097f3b2fb8b62baeca28a9c1304c66d53:7024
000000074a88c96450912b52e1d0bf5ccafa2ad0baad924aa25ccca93ac26c83:3a3b2e7f190c18f062a69a2a08add7dec737b8fae3e2fda787d98eb9dbbd4c1d:7013
0000000056ee7692aa3087e836b8f2c4b8f51d63fd35cb0aaa8dac045e15482b:d916e4898ba4cfed1762208a206038a05a360df7b5e8a0ad277cc44a58033ef6:6774
000000025d810e51f670cacf7cd527c7ff3da38a45ed0ac63ff5f0e7df8eca50:73253e6a5c5de7977f5c59f4c258dfad639782f1e1fb2cabebf2133af84548a4:6870
000000042f609069a09a28f4066eb197bd31c8b0a17b88dbfab60b1541197e64:d19c18c3d84e72769d80786d2c693a83ab501612985db769cb1f54951df8327b:6951
00000001c04c07c6e1b666eb6d5f65a4cb1bdcbaa56856018fbfb3e8fb18ab94:5035f9ac819684d9f44d074771f0c5bb69644cec0fbfe8fb2fbf3e715618ed14:6954
000000037bf8006fb5a0e319b103b419297461ce77861f883230e225c7ad1ae5:416cbe613bcc413410b3f888fee80c7593952c415aba5e49a7c576b136982366:7019
0000000052e6a4a7a1eed17907284a3199efdcf5226107abbdceb68ff375ffa2:b6febe5a1193e9301a2b70d6e6b84f8d8f7c5a8f15c8eed6f9d4902f19057fb0:7023
June 05, 2014, 10:00:23 AM
POOL STATS
slimcoin dcrypt 58 499635 25702 105 12 0 89 596.92 KH
Sandor111, the stats are not in real time are they ? There are more workers than 58.
Please confirm if only 12 blocks have been mined so far
slimcoin dcrypt 58 499635 25702 105 12 0 89 596.92 KH
Sandor111, the stats are not in real time are they ? There are more workers than 58.
Please confirm if only 12 blocks have been mined so far
Actually 16 blocks. 89 blocks are orphans because the pool was in the wrong fork 10 hours ago. After that sandor111 said everything works fine. But I don't understand why the pending blocks decrease but the confirm blocks doesn't increase. Ok it doesn't get confirm yet but where does it go ? Something wrong with the stats.
June 05, 2014, 09:24:45 AM
POOL STATS
slimcoin dcrypt 58 499635 25702 105 12 0 89 596.92 KH
Sandor111, the stats are not in real time are they ? There are more workers than 58.
Please confirm if only 12 blocks have been mined so far
slimcoin dcrypt 58 499635 25702 105 12 0 89 596.92 KH
Sandor111, the stats are not in real time are they ? There are more workers than 58.
Please confirm if only 12 blocks have been mined so far
June 05, 2014, 08:20:51 AM
I can confirm that he pays the bounties he offers.
Thanks!
Hopefully someone takes the task of adding rpcthreads soon. June 05, 2014, 08:19:56 AM
I tried to use minerd -dcrypt on the pool and I only get rejected...
you don't need to supply the algo when using slimminer, dcrypt is the default algo. however, the correct cmd line would be:
Code:
minerd -a dcrypt -o SERVER:PORT -u USER -p PASS
anyway
that wont work on the pool, you need to specify stratum, eg.
Code:
minerd -a dcrypt -o stratum+tcp://SERVER:PORT -u USER -p PASS
June 05, 2014, 08:18:27 AM
I tried to use minerd -dcrypt on the pool and I only get rejected...
you don't need to supply the algo when using slimminer, dcrypt is the default algo. however, the correct cmd line would be:
Code:
minerd -a dcrypt -o SERVER:PORT -u USER -p PASS
anyway
I am placing a new bounty of 0.15BTC (!!!!!!!!) if someone adds the rpcthreads function to git and it gets accepted by the dev. Deadline : 24h
I can confirm that he pays the bounties he offers.
June 05, 2014, 08:09:10 AM
I am placing a new bounty of 0.15BTC (!!!!!!!!) if someone adds the rpcthreads function to git and it gets accepted by the dev. Deadline : 24h
June 05, 2014, 08:02:35 AM
Just point my miner to the new pool.
Hope we can have the payout.
Hope we can have the payout.
I hope so too, there isn't a single confirmed block yet though.
Spread the load accross couple of wallets maybe ?
It has nothing to do with that, I have 3 wallets open already. Slimcoin itself just needs a huge number of block confirmations.
Not talking about immature blocks man, talking about pool shutting off every now and then
That was me, I have to restart to wallets/etc. after doing some updates to the pool.
BTW, ramdisk seems to be doing the trick. All is super fast now.
June 05, 2014, 08:00:51 AM
Just point my miner to the new pool.
Hope we can have the payout.
Hope we can have the payout.
I hope so too, there isn't a single confirmed block yet though.
Spread the load accross couple of wallets maybe ?
It has nothing to do with that, I have 3 wallets open already. Slimcoin itself just needs a huge number of block confirmations.
Not talking about immature blocks man, talking about pool shutting off every now and then
June 05, 2014, 07:59:48 AM
Just point my miner to the new pool.
Hope we can have the payout.
Hope we can have the payout.
I hope so too, there isn't a single confirmed block yet though.
Spread the load accross couple of wallets maybe ?
It has nothing to do with that, I have 3 wallets open already. Slimcoin itself just needs a huge number of block confirmations.
June 05, 2014, 07:56:44 AM
I tried to use minerd -dcrypt on the pool and I only get rejected...
June 05, 2014, 07:54:28 AM
Just point my miner to the new pool.
Hope we can have the payout.
Hope we can have the payout.
I hope so too, there isn't a single confirmed block yet though.
Spread the load accross couple of wallets maybe ? Dev should have contacted DSTORM about p2pool, hes got experience running pools, this is amateur hour
June 05, 2014, 07:50:27 AM
Just point my miner to the new pool.
Hope we can have the payout.
Hope we can have the payout.
I hope so too, there isn't a single confirmed block yet though.
June 05, 2014, 07:50:08 AM
Pool Algo Workers Valid Shares Invalid Shares Total Blocks Pending Confirmed Orphaned Hashrate
slimcoin dcrypt 59 408397 25203 101 8 0 89 643.60 KH
Zero confirmed blocks???
slimcoin dcrypt 59 408397 25203 101 8 0 89 643.60 KH
Zero confirmed blocks???
Jump to: