Author

Topic: NA - page 565. (Read 893616 times)

legendary
Activity: 1658
Merit: 1001
June 29, 2014, 02:42:37 AM
The wallet software only does CPU mining. You need to let your cudaminer connect with your wallet software (RPC interface) to do solo GPU mining. Your wallet software runs then as a private pool.

oke clear to me it is connecting with my wallet thanks for the info..

and can i also " do double ? i mean setgenerate true , so GPU and CPU in the same time ?


I don't see why not. Did you try?
sr. member
Activity: 616
Merit: 321
June 29, 2014, 02:35:35 AM
The wallet software only does CPU mining. You need to let your cudaminer connect with your wallet software (RPC interface) to do solo GPU mining. Your wallet software runs then as a private pool.

oke clear to me it is connecting with my wallet thanks for the info..

and can i also " do double ? i mean setgenerate true , so GPU and CPU in the same time ?


legendary
Activity: 1658
Merit: 1001
June 29, 2014, 02:28:54 AM
The wallet software only does CPU mining. You need to let your cudaminer connect with your wallet software (RPC interface) to do solo GPU mining. Your wallet software runs then as a private pool.
sr. member
Activity: 616
Merit: 321
June 29, 2014, 02:16:01 AM
question about solomining this coin, after making the config file guldencoin.conf what do i have to de with the wallet ?
 i know i have start the wallet with the -server option but wen i look at the debug windows getminininfo :

getmininginfo i see generate " false" do i have to put gen=1 in configuration file ? wen i setgenerate true in wallet my cpu go mining it and i just want my GPU mining this

with cudaminer running  i see in debug windows getmining info :

blocks" : 73034,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 16.70043859,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 463054683,
"pooledtx" : 0,
"testnet" : false

i in my cuda miner start bat running :
[2014-06-29 09:14:17] GPU #0: GeForce GTX 750, 229.62 khash/s
[2014-06-29 09:14:22] GPU #0: GeForce GTX 750, 229.63 khash/s
[2014-06-29 09:14:27] GPU #0: GeForce GTX 750, 229.77 khash/s
[2014-06-29 09:14:33] GPU #0: GeForce GTX 750, 229.18 khash/s
[2014-06-29 09:14:38] GPU #0: GeForce GTX 750, 229.63 khash/s
[2014-06-29 09:14:43] GPU #0: GeForce GTX 750, 229.50 khash/s
[2014-06-29 09:14:48] GPU #0: GeForce GTX 750, 229.41 khash/s
[2014-06-29 09:14:53] GPU #0: GeForce GTX 750, 231.49 khash/s
[2014-06-29 09:14:58] GPU #0: GeForce GTX 750, 230.71 khash/s

solo mining  guldencoin.conf as on page 1 like this :
rpcuser=username
rpcpassword=password
rpcport=9232
rpcallowip=127.0.0.1
server=1
daemon=1
listen=1
addnode=seed1.guldencoin.com
addnode=seed2.guldencoin.com
addnode=seed3.guldencoin.com
addnode=seed4.guldencoin.com
addnode=seed5.guldencoin.com
addnode=seed6.guldencoin.com
addnode=seed7.guldencoin.com  ect,ect

need some little help here to see if my config is oke to mine with my GPU only please ,

after a wile running i see now in wallet debug window this :



{
"blocks" : 73046,
"currentblocksize" : 2927,
"currentblocktx" : 2,
"difficulty" : 17.03426254,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 459779280,
"pooledtx" : 2,
"testnet" : false
}

is this oke ?


our projects guldencoin address : GcfkiZPaqMyNumezFVUgKqgYXEsLDu1FQM  / galgo support


sr. member
Activity: 458
Merit: 500
June 29, 2014, 12:37:48 AM
voting for coinwarz is like voting for your own death sentence these days.
sr. member
Activity: 332
Merit: 250
June 28, 2014, 01:56:52 PM
Did I miss something with the NLGcup? Because it's not possible anymore to bet on draw...

Matches won't end in draw anymore.. The following matches will be extended in time when there's no winner. I don't know the exact rules.. I think there will be 2x 15 minutes of game extension. And golden goal after that?

That is correct Geert, it's do or die now, there has to be a winner, if draw at full time when we have 30min extra time and if still a draw then penalty shootouts to decide the winner.

Thanks guys, I did not realise.
legendary
Activity: 924
Merit: 1000
June 28, 2014, 08:36:47 AM
Did I miss something with the NLGcup? Because it's not possible anymore to bet on draw...

Matches won't end in draw anymore.. The following matches will be extended in time when there's no winner. I don't know the exact rules.. I think there will be 2x 15 minutes of game extension. And golden goal after that?

That is correct Geert, it's do or die now, there has to be a winner, if draw at full time when we have 30min extra time and if still a draw then penalty shootouts to decide the winner.
sr. member
Activity: 409
Merit: 250
June 28, 2014, 07:47:03 AM
Did I miss something with the NLGcup? Because it's not possible anymore to bet on draw...

Matches won't end in draw anymore.. The following matches will be extended in time when there's no winner. I don't know the exact rules.. I think there will be 2x 15 minutes of game extension. And golden goal after that?
sr. member
Activity: 332
Merit: 250
June 28, 2014, 06:41:48 AM
Did I miss something with the NLGcup? Because it's not possible anymore to bet on draw...
legendary
Activity: 952
Merit: 1000
June 28, 2014, 04:58:19 AM
How about Dark Gravity Wave?

Has anyone got any objections towards that retarget method?

The point of the discussion was to alert the community that the listing of NLG on Coinwarz will only be detrimental to the coin and network.

There is no retargeting algo that will prevent a network from sticking when hit with 10X increase in hash-rate, the retargeting algo is doing its job to keep the average block time to the prescribed spec. Prevention is better than a cure, and that is focus on utility and user adoption, not increasing miner awareness.

Miners will naturally be attracted to NLG as it becomes more adopted and accepted. Attracting miners is easy, building a user base is many times harder.

As the network grows in size and maturity the threat of diff spikes and network stalls will decrease.

So KGW, Digishield, DGW... the point is to protect the coin until it is mature enough to handle the big bad world.

I agree with you and I don't vote on coinwarz anymore. KGW is good as it is and will be better and better when the network grows naturally in time. Good discussion though!
sr. member
Activity: 672
Merit: 250
June 28, 2014, 04:37:55 AM
How about Dark Gravity Wave?

Has anyone got any objections towards that retarget method?

The point of the discussion was to alert the community that the listing of NLG on Coinwarz will only be detrimental to the coin and network.

There is no retargeting algo that will prevent a network from sticking when hit with 10X increase in hash-rate, the retargeting algo is doing its job to keep the average block time to the prescribed spec. Prevention is better than a cure, and that is focus on utility and user adoption, not increasing miner awareness.

Miners will naturally be attracted to NLG as it becomes more adopted and accepted. Attracting miners is easy, building a user base is many times harder.

As the network grows in size and maturity the threat of diff spikes and network stalls will decrease.

So KGW, Digishield, DGW... the point is to protect the coin until it is mature enough to handle the big bad world.
full member
Activity: 392
Merit: 100
June 28, 2014, 03:56:21 AM
How about Dark Gravity Wave?

Has anyone got any objections towards that retarget method?
sr. member
Activity: 332
Merit: 250
June 28, 2014, 02:39:31 AM
Not sure your point... at the time of those spikes... POT was using the latest version of KGW(same version as NLG is using now)... I know... I was there mining POT. You can also ask 'Fuse' as I am part of the Criptoe Team... he will confirm the facts.

Go to Github and check the PotCoin commits... POT is now using Digishield for its block retargting algo... which is only slightly better than KGW at coping... which means it does not make any real world difference.

No simulation needed... that was how KGW reacted in the real world.

I am speaking from experience trying to protect NLG and ensure it succeeds.

24Kilo is correct.  Most coins have moved to DGW or Digishield in response to the shortcomings of KGW.  POT realized this and made the move after realizing that the newer KGW wasn't totally effective.  It did plug the timewarp hole(as far as we know).

While a move to Digishield would be beneficial in the long run, staying off the coin profitability sites will negate the need... for now.  The good news is that the total network hashrate is relatively low right now.  Making a move to Digishield would be easier to manage right now.  In addition, the code change is minimal.  I would say go for it.

For the time being though, Like 24Kilo mentioned, under the radar with organic traffic is the way to go.

-Fuse

Yep KGW is easy to manipulate (I tested it myself - sorry hardcore - and managed to get 75% of the coins in 50% of the time. Digishield is way more suited. We need proper protection, warning and organic growth.
sr. member
Activity: 332
Merit: 250
June 28, 2014, 02:35:23 AM
Voting on Coinwartz many times every day! So for sure, one day we will enter this one!

Within 3 or 4 weeks we should be there!

Price of NLG has stabilised and rising slowly but steady now. All buyorder numbers from 82 up to 101 filled, without gabs. Good sign, I think!

Don't let the figures fool you!! Every thing is filled because someone makes it look like it is filled. For instance there were big .5 BTC buy orders several times and zipp they are gone. Bought up you think? Nope, they are not in the historical transactions, so they are placed and canceled, placed and canceled. Thats the game, I mentioned before "buckle up and watch the show". Maybe I should add that you went down the rabbit hole when you entered the cryptoworld, nothing is what it looks like and were you see things is nothing...
hero member
Activity: 637
Merit: 500
June 27, 2014, 08:19:03 PM
Not sure your point... at the time of those spikes... POT was using the latest version of KGW(same version as NLG is using now)... I know... I was there mining POT. You can also ask 'Fuse' as I am part of the Criptoe Team... he will confirm the facts.

Go to Github and check the PotCoin commits... POT is now using Digishield for its block retargting algo... which is only slightly better than KGW at coping... which means it does not make any real world difference.

No simulation needed... that was how KGW reacted in the real world.

I am speaking from experience trying to protect NLG and ensure it succeeds.

24Kilo is correct.  Most coins have moved to DGW or Digishield in response to the shortcomings of KGW.  POT realized this and made the move after realizing that the newer KGW wasn't totally effective.  It did plug the timewarp hole(as far as we know).

While a move to Digishield would be beneficial in the long run, staying off the coin profitability sites will negate the need... for now.  The good news is that the total network hashrate is relatively low right now.  Making a move to Digishield would be easier to manage right now.  In addition, the code change is minimal.  I would say go for it.

For the time being though, Like 24Kilo mentioned, under the radar with organic traffic is the way to go.

-Fuse

As long us big holders release coins to be sold when the market needs it at a steady rate while allowing price growth. I am personally holding my NLG for 2 years, this is one coin with a future esp if devs are pushing this coin and giving us constant updates at current prices, but if people are needing NLG and there is no sellers I will make sure to always put up sell orders.
legendary
Activity: 1582
Merit: 1002
HODL for life.
June 27, 2014, 08:05:25 PM
Not sure your point... at the time of those spikes... POT was using the latest version of KGW(same version as NLG is using now)... I know... I was there mining POT. You can also ask 'Fuse' as I am part of the Criptoe Team... he will confirm the facts.

Go to Github and check the PotCoin commits... POT is now using Digishield for its block retargting algo... which is only slightly better than KGW at coping... which means it does not make any real world difference.

No simulation needed... that was how KGW reacted in the real world.

I am speaking from experience trying to protect NLG and ensure it succeeds.

24Kilo is correct.  Most coins have moved to DGW or Digishield in response to the shortcomings of KGW.  POT realized this and made the move after realizing that the newer KGW wasn't totally effective.  It did plug the timewarp hole(as far as we know).

While a move to Digishield would be beneficial in the long run, staying off the coin profitability sites will negate the need... for now.  The good news is that the total network hashrate is relatively low right now.  Making a move to Digishield would be easier to manage right now.  In addition, the code change is minimal.  I would say go for it.

For the time being though, Like 24Kilo mentioned, under the radar with organic traffic is the way to go.

-Fuse
hero member
Activity: 637
Merit: 500
June 27, 2014, 07:59:08 PM

Here is the program I wrote to calculate the number of coins sent to miner addresses:
https://gist.github.com/GeertJohan/b9cdf1e5ffb815b776d8


Keep up with the good work Geert! Your updates are wonderful to see.
hero member
Activity: 637
Merit: 500
June 27, 2014, 07:58:14 PM
[..]

KGW cannot cope with such a situation... it actually makes things worse... because the difficulty falls so low after such an incident that it can hours or even days for the diff to resettle... and most often because of the extreme fall in difficulty after an episode... it triggers the multi-pools again and so it becomes a death spiral.

PotCoin(POT) was taken off-line for nearly 24 hours because of this and the dev team had to negotiate with multi-pool admin to solve the problem...

[...]

Hmm good point.. I think I'll try to run some simulations on KGW to figure out how it reacts under those circumstances...
Thanks!

Not sure your point... at the time of those spikes... POT was using the latest version of KGW(same version as NLG is using now)... I know... I was there mining POT. You can also ask 'Fuse' as I am part of the Criptoe Team... he will confirm the facts.

Go to Github and check the PotCoin commits... POT is now using Digishield for its block retargting algo... which is only slightly better than KGW at coping... which means it does not make any real world difference.

No simulation needed... that was how KGW reacted in the real world.

I am speaking from experience trying to protect NLG and ensure it succeeds.

+1
Coinmarketcap is for investors
Coinwarz is for miners

sr. member
Activity: 672
Merit: 250
June 27, 2014, 07:06:05 PM
[..]

KGW cannot cope with such a situation... it actually makes things worse... because the difficulty falls so low after such an incident that it can hours or even days for the diff to resettle... and most often because of the extreme fall in difficulty after an episode... it triggers the multi-pools again and so it becomes a death spiral.

PotCoin(POT) was taken off-line for nearly 24 hours because of this and the dev team had to negotiate with multi-pool admin to solve the problem...

[...]

Hmm good point.. I think I'll try to run some simulations on KGW to figure out how it reacts under those circumstances...
Thanks!

Not sure your point... at the time of those spikes... POT was using the latest version of KGW(same version as NLG is using now)... I know... I was there mining POT. You can also ask 'Fuse' as I am part of the Criptoe Team... he will confirm the facts.

Go to Github and check the PotCoin commits... POT is now using Digishield for its block retargting algo... which is only slightly better than KGW at coping... which means it does not make any real world difference.

No simulation needed... that was how KGW reacted in the real world.

I am speaking from experience trying to protect NLG and ensure it succeeds.
sr. member
Activity: 409
Merit: 250
June 27, 2014, 07:05:14 PM

Here is the program I wrote to calculate the number of coins sent to miner addresses:
https://gist.github.com/GeertJohan/b9cdf1e5ffb815b776d8
Jump to: