|
1G24AeCYTqsfbiFtFAU5nVG1zwdojtHCAD thanks man!
|
|
|
|
reward to 100 can improve this?
I think dev can buy much vps to see how the number of reward.
100 is too low.
Or you can set one day bounty to all node.
like the bitcoin difficulty.
100-150 is too low
miner always have risk when the price is down.
I can't find <$5 vps to buy one hour or one day.
If buy month,they didn't have risk to lose money?
Check this out https://en.bitcoin.it/wiki/Comparison_of_VPS_providershttps://apexy.com/plans.html this one has $10 year plan. This mean 83 cents a month. $5 month and most of them is $5/month up. |
|
|
|
I didn't get any 666NHZ for the 29th Sept. Is this normal?
these node bounties killing this coin. Everybody just dumping. someone has hundreds vps and that's not fear. we are investing but they are just dumping. simple math: $3 monthly each vps and 100 vps gets daily 66600 NHZ, monthly 1.980.000 nhz avarage at 150 satoshi . total 2.97 btc minus $300 vps cost. Boom more than 2 btc profit. I'm not doing this shit because I do not want to kill this coin. I see your logic on this one and agree. This is definitely something that needs to be reconsidered and sorted out, to avoid any future hiccups. 500 too much. 100 maybe or associate each account for just one ip and( not or) one node. Each node must be have min 100.000 NHZ or more and must not act for a week. will see how NHZ price climbing. Just adjust the reward to the breakeven monthly VPS price. ((3/400)/0.00000200)/30 = 125NHZ per day max atm Include this daily calculation in the script and calculate based on current BTC/USD and BTC/NHZ price. Ezpz. These are quite reasonable solutions... But as we all know this needs a lot thinking because there are many factors to be considered. How much is your vps monthly costs? my vps price is $5 one month. but can't get more machine like digitocean. and with the uncomplete system I only get two day bounty in 1 week? And you must know node bouty must be profitable. Not like ezpz said.If so,why I make node ,I can buy nhz. if so,why I buy nhz,I can buy more cheap coin. you think everyone can buy $3 vps easily?I think I can't. waste a lot of time to earn $3 value nhz during one month with manage own vps and used $3. just to buy.. most people have to buy $5 vps.oh waste time to lose $2.. |
|
|
|
I didn't get any 666NHZ for the 29th Sept. Is this normal?
these node bounties killing this coin. Everybody just dumping. someone has hundreds vps and that's not fear. we are investing but they are just dumping. simple math: $3 monthly each vps and 100 vps gets daily 66600 NHZ, monthly 1.980.000 nhz avarage at 150 satoshi . total 2.97 btc minus $300 vps cost. Boom more than 2 btc profit. I'm not doing this shit because I do not want to kill this coin. I see your logic on this one and agree. This is definitely something that needs to be reconsidered and sorted out, to avoid any future hiccups. 500 too much. 100 maybe or associate each account for just one ip and( not or) one node. Each node must be have min 100.000 NHZ or more and must not act for a week. will see how NHZ price climbing. Just adjust the reward to the breakeven monthly VPS price. ((3/400)/0.00000200)/30 = 125NHZ per day max atm Include this daily calculation in the script and calculate based on current BTC/USD and BTC/NHZ price. Ezpz. These are quite reasonable solutions... But as we all know this needs a lot thinking because there are many factors to be considered. How much is your vps monthly costs? my vps price is $5 one month. but can't get more machine like digitocean. and with the uncomplete system I only get two day bounty in 1 week? And you must know node bouty must be profitable. Not like ezpz said.If so,why I make node ,I can buy nhz. if so,why I buy nhz,I can buy more cheap coin. |
|
|
|
|
just test youself.
I think the amount of one day bounty can be set
like 1000 nhz
to
1000 node everyone:1nhz
100 node everyone:10nhz
if can't do that,just to test to set node.
no one want to set node to lose money.
you know the dev set the node bounty just want to make the network well and attract more people to join us.
If there is no profit,how can we reach this.
|
|
|
|
I didn't get any 666NHZ for the 29th Sept. Is this normal?
The staking / bounty scripts are disabled right now while we are fixing an issue with the scripts taking so long for payouts, which was a result of them getting overloaded due to the 300% increase in nodes in the past week. I will be providing a more technical update + solution soon. Okay, thanks for the update on this. these node bounties killing this coin. Everybody just dumping. someone has hundreds vps and that's not fear. we are investing but they are just dumping. simple math: $3 monthly each vps and 100 vps gets daily 66600 NHZ, monthly 1.980.000 nhz avarage at 150 satoshi . total 2.97 btc minus $300 vps cost. Boom more than 2 btc profit. I'm not doing this shit because I do not want to kill this coin. I see your logic on this one and agree. This is definitely something that needs to be reconsidered and sorted out, to avoid any future hiccups. This was something I addressed in the roadmap. We will be constantly addressing this issue by monitoring the node network and price. We will be reducing the reward from 666 to 500 given the current price. IMO, If you apply variable node rewards pegged to NHZ performance, it will simply not do. 100-150 should be the correct node reward amount. By keeping the reward price low (and fixed), we will avoid node holder dumps (which results to lower coin price) + any price manipulation (so node rewards increase/decrease). In other words by keeping node rewards low&fixed = everyone will be working in increasing NHZ value (as it should) and everyone wins; node holders, investors etc. etc. you will see very small nodes.Why I set node to lose money?just to buy nhz is better choice. you know why set the node bounty. you know why there is so many miners? you just want to be investor and went out when the price is high? no care the network,no care how many people to join this game. I think you just can't set node easily and don't want other people to earn nhz! Look its quite simple, look at it in macro economic terms: Nodes are needed to secure the network and also bounties are needed as an incentive to those contributing to the network. The question is how much should you reward a node? Too much leads to dumping and that affects the price. Winner in this case is the ''miner'' who makes the quick profit. Generous node bounties end up NHZ shooting its own foot. If the coin dies so will your ''mining profits'' reward to 100 can improve this? I think dev can buy much vps to see how the number of reward. 100 is too low. Or you can set one day bounty to all node. like the bitcoin difficulty. 100-150 is too low miner always have risk when the price is down. I can't find <$5 vps to buy one hour or one day. If buy month,they didn't have risk to lose money? |
|
|
|
I didn't get any 666NHZ for the 29th Sept. Is this normal?
The staking / bounty scripts are disabled right now while we are fixing an issue with the scripts taking so long for payouts, which was a result of them getting overloaded due to the 300% increase in nodes in the past week. I will be providing a more technical update + solution soon. Okay, thanks for the update on this. these node bounties killing this coin. Everybody just dumping. someone has hundreds vps and that's not fear. we are investing but they are just dumping. simple math: $3 monthly each vps and 100 vps gets daily 66600 NHZ, monthly 1.980.000 nhz avarage at 150 satoshi . total 2.97 btc minus $300 vps cost. Boom more than 2 btc profit. I'm not doing this shit because I do not want to kill this coin. I see your logic on this one and agree. This is definitely something that needs to be reconsidered and sorted out, to avoid any future hiccups. This was something I addressed in the roadmap. We will be constantly addressing this issue by monitoring the node network and price. We will be reducing the reward from 666 to 500 given the current price. IMO, If you apply variable node rewards pegged to NHZ performance, it will simply not do. 100-150 should be the correct node reward amount. By keeping the reward price low (and fixed), we will avoid node holder dumps (which results to lower coin price) + any price manipulation (so node rewards increase/decrease). In other words by keeping node rewards low&fixed = everyone will be working in increasing NHZ value (as it should) and everyone wins; node holders, investors etc. etc. you will see very small nodes.Why I set node to lose money?just to buy nhz is better choice. you know why set the node bounty? you know why there is so many btc miners? you just want to be investor and went out when the price is high? no care the network,no care how many people to join this game. I think you just can't set node easily and don't want other people to earn nhz! |
|
|
|
I didn't get any 666NHZ for the 29th Sept. Is this normal?
The staking / bounty scripts are disabled right now while we are fixing an issue with the scripts taking so long for payouts, which was a result of them getting overloaded due to the 300% increase in nodes in the past week. I will be providing a more technical update + solution soon. Okay, thanks for the update on this. these node bounties killing this coin. Everybody just dumping. someone has hundreds vps and that's not fear. we are investing but they are just dumping. simple math: $3 monthly each vps and 100 vps gets daily 66600 NHZ, monthly 1.980.000 nhz avarage at 150 satoshi . total 2.97 btc minus $300 vps cost. Boom more than 2 btc profit. I'm not doing this shit because I do not want to kill this coin. I see your logic on this one and agree. This is definitely something that needs to be reconsidered and sorted out, to avoid any future hiccups. This was something I addressed in the roadmap. We will be constantly addressing this issue by monitoring the node network and price. We will be reducing the reward from 666 to 500 given the current price. 500 too much. 100 maybe or associate each account for just one ip and( not or) one node. Each node must be have min 100.000 NHZ or more and must not act for a week. will see how NHZ price climbing. Just adjust the reward to the breakeven monthly VPS price. ((3/400)/0.00000200)/30 = 125NHZ per day max atm Include this daily calculation in the script and calculate based on current BTC/USD and BTC/NHZ price. Ezpz. you mean you can find much $3 vps?.. I can't find..plz give link. you mean let the node never have profit,so why it's bounty? |
|
|
|
Just wanted to post some 750 NON TI hashrates:
-on djm's cryptonitev3 3850 khash
-quark 4100 khash
They are from gigabyte and overclock like hell. I have them stable on +213 core and +454 mem with +12mv. I cant get my ti's over +86core.
Did you have a problem with the non ti and cryptonite, I received a PM yesterday from a guy who didn't want to post on the thread reporting problem I found 750 not ti get error like [2014-08-18 03:02:07] Starting Stratum on stratum+tcp://xcnpool-apac.1gh.com:733
3
[2014-08-18 03:02:07] Binding thread 0 to cpu 0
[2014-08-18 03:02:07] Binding thread 1 to cpu 1
[2014-08-18 03:02:07] Binding thread 5 to cpu 5
[2014-08-18 03:02:07] Binding thread 2 to cpu 2
[2014-08-18 03:02:08] Stratum detected new block
[2014-08-18 03:02:10] GPU #4: result for nonce $00000000 does not validate on CP
U! vhash64 47aac607 and htarg 00000dcc
data 0 46821563 1 17bce19a
[2014-08-18 03:02:10] GPU #0: result for nonce $00000000 does not validate on CP
U! vhash64 47aac607 and htarg 00000dcc
data 2 f3c15d68 3 7c1e6957
data 4 0b88b2f4 5 69efdc6a
[2014-08-18 03:02:10] GPU #3: result for nonce $00000000 does not validate on CP
U! vhash64 47aac607 and htarg 00000dcc
data 6 013e4601 7 00000000
[2014-08-18 03:02:10] GPU #1: result for nonce $00000000 does not validate on CP
U! vhash64 47aac607 and htarg 00000dcc
data 8 3add2f57 9 f74fbab8
[2014-08-18 03:02:10] GPU #5: result for nonce $00000000 does not validate on CP
U! vhash64 47aac607 and htarg 00000dcc
data 10 b862e28b 11 312407e7
[2014-08-18 03:02:10] GPU #2: result for nonce $00000000 does not validate on CP
U! vhash64 47aac607 and htarg 00000dcc
data 12 f1540588 13 dec4ce03
data 14 ddf8cef2 15 d3461964
data 16 9164c6c3 17 37db7ab4
data 18 86c7511c 19 62aa516d
data 20 701b4110 21 3ed2a7ff
data 22 14882437 23 0f0da1d1
data 24 53f0fc19 25 00000000
data 26 0000840e 27 00000000
data 28 00c0000a 29 00000000
data 30 00200001 31 009eea40
pdata 0 00000000 1 00200001
pdata 2 009eea40 3 00000002
pdata 4 009eeb00 5 00200150
pdata 6 0000000f 7 003327d0
pdata 8 00000000 9 0000000f
pdata 10 04cbf808 11 0000000d
pdata 12 009eea80 13 00000001
pdata 14 00000000 15 0020f8c8
pdata 16 00000001 17 00000000
pdata 18 0020f8d8 19 00000001
pdata 20 00000000 21 0020f8e8
pdata 22 00000001 23 00000000
pdata 24 0020f8f8 25 00000001
pdata 26 00000000 27 0020f908
pdata 28 00000001 29 00000000
pdata 30 0020f918 31 00000001
sha256[0]=2e dd 8b 27 sha512[0]=db bc 5a 93 keccak[0]=96 70 6d cb whirlpool[2][0
]=e3 13 69 22 haval[0]=cc b9 9c 34 tiger[0]=75 de aa 98 ripemd[0]=87 98 49 fe
sha256[1]=85 51 b7 f7 sha512[1]=69 01 05 91 keccak[1]=3a 88 b8 ae whirlpool[2][1
]=ac 6f 12 8b haval[1]=56 07 42 95 tiger[1]=c3 2e 30 68 ripemd[1]=53 18 50 35
sha256[2]=53 42 36 77 sha512[2]=ab ec f6 c4 keccak[2]=7d 03 ca c5 whirlpool[2][2
]=50 57 54 92 haval[2]=69 48 a4 ff tiger[2]=3a f3 ef 57 ripemd[2]=a9 92 44 45
sha256[3]=42 27 16 65 sha512[3]=0c b5 4f 91 keccak[3]=09 cd 9b 9e whirlpool[2][3
]=00 1d a6 0a haval[3]=48 91 cc 50 tiger[3]=9f 5c fd ba ripemd[3]=02 99 21 ce
sha256[4]=8c bf b5 15 sha512[4]=f9 50 59 9e keccak[4]=76 66 d5 30 whirlpool[2][4
]=18 61 c4 70 haval[4]=84 7e 7c 87 tiger[4]=dc c0 e5 28 ripemd[4]=a1 a6 3b 30
sha256[5]=41 f3 70 01 sha512[5]=a3 2f 72 d6 keccak[5]=ac e8 9e ad whirlpool[2][5
]=66 c0 43 ec haval[5]=1b e1 21 b4 tiger[5]=44 14 24 61 ripemd[5]=00 00 00 00
sha256[6]=65 34 30 b4 sha512[6]=75 e5 4e 0e keccak[6]=6d c1 b9 05 whirlpool[2][6
]=0a 23 63 7f haval[6]=09 b7 67 f1 tiger[6]=00 00 00 00 ripemd[6]=00 00 00 00
sha256[7]=65 53 49 f2 sha512[7]=12 d1 87 73 keccak[7]=1d 85 3d 0d whirlpool[2][7
]=3b e4 4a c9 haval[7]=d4 ec 0f a9 tiger[7]=00 00 00 00 ripemd[7]=00 00 00 00
sha256[8]=00 00 00 00 sha512[8]=8e 2d 21 95 keccak[8]=c4 30 17 9c whirlpool[2][8
]=84 e7 59 4a haval[8]=00 00 00 00 tiger[8]=00 00 00 00 ripemd[8]=00 00 00 00
sha256[9]=00 00 00 00 sha512[9]=d9 5f 59 60 keccak[9]=77 28 79 da whirlpool[2][9
]=a5 79 90 c3 haval[9]=00 00 00 00 tiger[9]=00 00 00 00 ripemd[9]=00 00 00 00
sha256[10]=00 00 00 00 sha512[10]=14 cd bc 2a keccak[10]=1b 50 7d 24 whirlpool[2
][10]=d4 26 94 3f haval[10]=00 00 00 00 tiger[10]=00 00 00 00 ripemd[10]=00 00 0
0 00
sha256[11]=00 00 00 00 sha512[11]=64 ea 82 37 keccak[11]=c8 52 21 9e whirlpool[2
][11]=73 cd 50 5f haval[11]=00 00 00 00 tiger[11]=00 00 00 00 ripemd[11]=00 00 0
0 00
sha256[12]=00 00 00 00 sha512[12]=36 3a 83 49 keccak[12]=12 da b9 3a whirlpool[2
][12]=1b 4e 35 37 haval[12]=00 00 00 00 tiger[12]=00 00 00 00 ripemd[12]=00 00 0
0 00
sha256[13]=00 00 00 00 sha512[13]=4d a6 66 b9 keccak[13]=0a c3 c7 f8 whirlpool[2
][13]=4c 42 6b 04 haval[13]=00 00 00 00 tiger[13]=00 00 00 00 ripemd[13]=00 00 0
0 00
sha256[14]=00 00 00 00 sha512[14]=4d cd 2c d1 keccak[14]=24 be d1 1e whirlpool[2
][14]=3a 07 dc 0e haval[14]=00 00 00 00 tiger[14]=00 00 00 00 ripemd[14]=00 00 0
0 00
sha256[15]=00 00 00 00 sha512[15]=e8 fd 35 56 keccak[15]=70 7c 65 1c whirlpool[2
][15]=33 82 9d 1b haval[15]=00 00 00 00 tiger[15]=00 00 00 00 ripemd[15]=00 00 0
0 00
data 0 46821563 1 17bce19a
[2014-08-18 03:02:10] GPU #4: GeForce GTX 750, 975.37 khash/s
data 2 f3c15d68 3 7c1e6957
[2014-08-18 03:02:10] GPU #4: result for nonce $00000000 does not validate on CP
U! vhash64 47aac607 and htarg 00000dcc
data 4 0b88b2f4 5 69efdc6a
data 6 013e4601 7 00000000
data 8 3add2f57 9 f74fbab8
data 10 b862e28b 11 312407e7
data 12 f1540588 13 dec4ce03
data 14 ddf8cef2 15 d3461964
data 16 9164c6c3 17 37db7ab4
data 18 86c7511c 19 62aa516d
data 20 701b4110 21 3ed2a7ff
data 22 14882437 23 0f0da1d1
data 24 53f0fc19 25 00000000
data 26 0000840e 27 00000000
data 28 00c0000a 29 00000000 |
|
|
|
|
2014-Aug-15 15:06:25.035440 [RPC1]Failed to store scratchpad, error: basic_ios::clear
rpc store scatchpad failed,what can i do.
rpc return:
{ status: 'BUSY' }
resolved
|
|
|
|
|
I'll test more..I waited 10min and no hash ...
|
|
|
|
|
[2014-08-14 12:05:29] GPU #2: result for nonce $00000000 does not validate on CP
U! vhash64 b641d601 and htarg 00000df7
。。is it right with ccminer m7 algo?
|
|
|
|
|
[2014-08-14 11:28:09] 6 miner threads started, using 'wildkeccak_ocl' algorithm.
so sad,just run after find gpu and got error..
alert minerd.exe is pause
tested with my 750 and 270x,win8 and win7,bbr.farm,my pool,cncoin pool...
|
|
|
|
You can use my repo with simpleminer updated with cryptozoidberg's fixes so it runs better. https://github.com/clintar/boolberry-opencl until mbk pulls those changes in. If you can't get it working following mbk's instructions in the README.md, try cmake -DOPENCL_LIBRARY=/usr/lib/libOpenCL.so
make or cmake -DOPENCL_LIBRARY=/usr/lib64/libOpenCL.so
make
that's how ive had to get it compiling on some nvidia machines. then, after it's started compiling i break with ctrl-c and do build/release/src
make -j4 simpleminer
cd ../../..
then to get the wild_kecak.cl file for nvidia, do: wget https://ottrbutt.com/tmp/wild_keccak_nv.cl -O wild_keccak.cl or for amd: wget https://ottrbutt.com/tmp/wild_keccak_nv.cl -O wild_keccak.cl then to run it src/simpleminer --pool-addr cncoin.farm:1111 --login 1GU1ZLjjkeAYyGDkq1NebLcSq4BQA37ZTSqoXG5zfDkQdTjb71Tma8vNsqJ3uxRdrKe89b6josHBF1oxaxovPPYy47vN4CD --pass x --mining-threads 1 --device 0 --remote_scratchpad http://cncoin.farm/scratchpad.bin --local_scratchpad scratchpad.bin replacing your address, pool info, and paths of course. Can you share compiled miner.. I think share miner can improve much hashes in pool and let the price go higher |
|
|
|
|
Thanks~,I made it ok now.speed up with your cl,~ Thanks !!!!!
|
|
|
|
|
I tested amd driver must be 14.6
what version Nvidia driver will be ok?
|
|
|
|
bbr pool code is not stable.
Many bugs is fixed by zone117x.
Merge the newest code node-cryptonote-pool will help more pools online.
You want not stable, eh? https://github.com/clintar/node-boolberry-poolIt has my attempt at making it workwith node-crytponote-pool. It works mostly, but I haven't figured out why the boolbd daemon rejects some blocks when testing on testnet (rejecting blocks seems pretty bad) Compare with crypto_zoidberg's and zone117x's,tested with new cryptonote coin like oec. The newest code by zone117x is stable, no bad hashes. Merge the newest change is better. |
|
|
|
|
bbr pool code is not stable.
Many bugs is fixed by zone117x.
Merge the newest code node-cryptonote-pool will help more pools online.
|
|
|
|
|
Show Posts
