Author

Topic: Nexus - Pure SHA3 + CPU/GPU + nPoS + 15 Active Innovations + More to Come - page 292. (Read 785531 times)

legendary
Activity: 868
Merit: 1058
Creator of Nexus http://nexus.io
Everything with Coinshield is quite transparent, you just need to do some reading  Wink

If you're talking about the supply being at 83%, it will get to 100% in time. If you notice it is increasing a little bit everyday.
Viz.
hero member
Activity: 672
Merit: 500
Banned: For Your Protection
This coin I feel is intended to deceive the calculation capacity,
The development of take all is force to dig other coins
Yes, when you hope, DEV theft our stress
I only got three days to give it up, there were people dig this?


What???

Translation: "Whoa! That was some gooood weed, man!!!"
full member
Activity: 224
Merit: 100
This coin I feel is intended to deceive the calculation capacity,
The development of take all is force to dig other coins
Yes, when you hope, DEV theft our stress
I only got three days to give it up, there were people dig this?


What???
member
Activity: 81
Merit: 10
This coin I feel is intended to deceive the calculation capacity,
The development of take all is force to dig other coins
Yes, when you hope, DEV theft our stress
I only got three days to give it up, there were people dig this?
newbie
Activity: 46
Merit: 0
@olajos

I'm not sure what your issue is. It seems as if your cards are running at 30 MH/s each. They should be closer to 39 MH/s each.

I'm currently working on a better interface for the miner. One where you can easily see the hash rate and info for individual cards.

I might have it done by Sunday but Thanksgiving will probably push it into next week.
hm... I don`t know where is the problem. I have 3 rig
1: 4x280x                 117-8 kh
2: 4x280x                 113-4 kh
3: 3x290x+1x280x     146-7 kh

full member
Activity: 224
Merit: 100
@olajos

I'm not sure what your issue is. It seems as if your cards are running at 30 MH/s each. They should be closer to 39 MH/s each.

I'm currently working on a better interface for the miner. One where you can easily see the hash rate and info for individual cards.

I might have it done by Sunday but Thanksgiving will probably push it into next week.
newbie
Activity: 46
Merit: 0
Ok I have a new build of SKMiner for Win x64!


I fixed the slow down issue, mainly caused by memory leaks.

My R9 280x ran for 6.5 hours last night and found 5 blocks. It was still running at the same speed this morning, 41 MH/s.

I put the new build up on my dropbox here:


https://www.dropbox.com/s/h2lcngoudtbuv5w/SKMiner.7z?dl=0



I will update the source on my github later tonight.



Hello.
I am running miners fine 2 days now, but with lower speed. Please some advice what to check.
4x280x running with 120000 kh
thanks

What are your config settings?

"algorithm" : "sk1024_djm",
   "gpu-engine" : "1100",
   "gpu-memclock" : "1550",
   "gpu-shaders" : "2048",
   "gpu-threads" : "1",
   "gpu-vddc" : "0",
   "gpu-powertune" : "0",
   "intensity" : "22",
   "xintensity" : "0",
   "rawintensity" : "0",
   "thread-concurrency" : "8192",
   "lookup-gap" : "2",
   "worksize" : "64",
   "temp-target" : "75",
   "temp-overheat" : "80",
   "temp-cutoff" : "95",
   "auto-engine" : "false",
   "auto-fan" : "false",
   "submit-stale" : "false",
   "vectors" : "1"
}
Also tried with worksize 256. Same speed. Maybe a lilbit slower


Hmmm...

It might just be that you're pushing your cards too hard.

try

"gpu-engine" : "1050"

and

"gpu-memclock" : "1500"


"worksize" : "256" should be good.


Also make sure you have the latest version of the miner. If you are using the one from the download above then you're good.

I am using latest version. tried clock 1050 and 1500 but same
legendary
Activity: 868
Merit: 1058
Creator of Nexus http://nexus.io
Not yet, this process will require a lot of community involvement.
Let alone I'm still building the Infrastructure to support such action  Wink

We'll see what time brings.


--------------------------------------


New Release of Prime Solo Miner
Source Code [Github]

Windows Binary x86
Windows Binary x64


Features Meter Data, protocol upgrades, etc.
Viz.
full member
Activity: 224
Merit: 100
Hey yall still destroying coins?
full member
Activity: 224
Merit: 100
Ok I have a new build of SKMiner for Win x64!


I fixed the slow down issue, mainly caused by memory leaks.

My R9 280x ran for 6.5 hours last night and found 5 blocks. It was still running at the same speed this morning, 41 MH/s.

I put the new build up on my dropbox here:


https://www.dropbox.com/s/h2lcngoudtbuv5w/SKMiner.7z?dl=0



I will update the source on my github later tonight.

Hello.
I am running miners fine 2 days now, but with lower speed. Please some advice what to check.
4x280x running with 120000 kh
thanks

What are your config settings?

"algorithm" : "sk1024_djm",
   "gpu-engine" : "1100",
   "gpu-memclock" : "1550",
   "gpu-shaders" : "2048",
   "gpu-threads" : "1",
   "gpu-vddc" : "0",
   "gpu-powertune" : "0",
   "intensity" : "22",
   "xintensity" : "0",
   "rawintensity" : "0",
   "thread-concurrency" : "8192",
   "lookup-gap" : "2",
   "worksize" : "64",
   "temp-target" : "75",
   "temp-overheat" : "80",
   "temp-cutoff" : "95",
   "auto-engine" : "false",
   "auto-fan" : "false",
   "submit-stale" : "false",
   "vectors" : "1"
}
Also tried with worksize 256. Same speed. Maybe a lilbit slower


Hmmm...

It might just be that you're pushing your cards too hard.

try

"gpu-engine" : "1050"

and

"gpu-memclock" : "1500"


"worksize" : "256" should be good.


Also make sure you have the latest version of the miner. If you are using the one from the download above then you're good.
legendary
Activity: 868
Merit: 1058
Creator of Nexus http://nexus.io
Thanks for the feedback mumus  Smiley

Viz.
legendary
Activity: 1512
Merit: 1000
quarkchain.io
You could try 14.11.2beta driver , but be careful
newbie
Activity: 46
Merit: 0
Ok I have a new build of SKMiner for Win x64!


I fixed the slow down issue, mainly caused by memory leaks.

My R9 280x ran for 6.5 hours last night and found 5 blocks. It was still running at the same speed this morning, 41 MH/s.

I put the new build up on my dropbox here:


https://www.dropbox.com/s/h2lcngoudtbuv5w/SKMiner.7z?dl=0



I will update the source on my github later tonight.

Hello.
I am running miners fine 2 days now, but with lower speed. Please some advice what to check.
4x280x running with 120000 kh
thanks

What are your config settings?

"algorithm" : "sk1024_djm",
   "gpu-engine" : "1100",
   "gpu-memclock" : "1550",
   "gpu-shaders" : "2048",
   "gpu-threads" : "1",
   "gpu-vddc" : "0",
   "gpu-powertune" : "0",
   "intensity" : "22",
   "xintensity" : "0",
   "rawintensity" : "0",
   "thread-concurrency" : "8192",
   "lookup-gap" : "2",
   "worksize" : "64",
   "temp-target" : "75",
   "temp-overheat" : "80",
   "temp-cutoff" : "95",
   "auto-engine" : "false",
   "auto-fan" : "false",
   "submit-stale" : "false",
   "vectors" : "1"
}
Also tried with worksize 256. Same speed. Maybe a lilbit slower
full member
Activity: 224
Merit: 100
Ok I have a new build of SKMiner for Win x64!


I fixed the slow down issue, mainly caused by memory leaks.

My R9 280x ran for 6.5 hours last night and found 5 blocks. It was still running at the same speed this morning, 41 MH/s.

I put the new build up on my dropbox here:


https://www.dropbox.com/s/h2lcngoudtbuv5w/SKMiner.7z?dl=0



I will update the source on my github later tonight.

Hello.
I am running miners fine 2 days now, but with lower speed. Please some advice what to check.
4x280x running with 120000 kh
thanks

What are your config settings?
sr. member
Activity: 291
Merit: 250


1.0.1d - Release: Updates to the UI. Added Immature label. Values of 0 CSD are ommited from the UI. Added Coinbase Rewards to Debug Console, Updated the Difficulty Value to be Current Difficulty. Stability Issues Resolved.

Ubuntu 1.0.1d - Release
Windows 1.0.1d - Release



Thank You,
Viz.

Thank you for the update. I upgraded all my nodes. Also the previous 1.0.1d beta version was stable.
newbie
Activity: 46
Merit: 0
Ok I have a new build of SKMiner for Win x64!


I fixed the slow down issue, mainly caused by memory leaks.

My R9 280x ran for 6.5 hours last night and found 5 blocks. It was still running at the same speed this morning, 41 MH/s.

I put the new build up on my dropbox here:


https://www.dropbox.com/s/h2lcngoudtbuv5w/SKMiner.7z?dl=0



I will update the source on my github later tonight.

Hello.
I am running miners fine 2 days now, but with lower speed. Please some advice what to check.
4x280x running with 120000 kh
thanks
legendary
Activity: 868
Merit: 1058
Creator of Nexus http://nexus.io
https://coin-swap.net/market/CSD/BTC

Low Volume, so you'll get a good Price  Wink
Viz.
legendary
Activity: 1400
Merit: 1000
Is there  an exchange for this coin?
legendary
Activity: 868
Merit: 1058
Creator of Nexus http://nexus.io
mumus,

I'm looking through the seed nodes and don't see this. It could be an attacker trying to fork your nodes, I haven't seen more than 7 connections on any of my nodes. I have seen some people flooding seed nodes with connections, so this could be a clever attack to try and make their own forked chain. It doesn't cause any harm as the Main Chain is locked with Checkpoints, just annoyances if your nodes gets caught in their fork.

Ah I see it, someone is trying to build their own chain from Block 63775 with their own transactions: This chain is currently being rejected.
It could also be the user still using Core 1.0.1. Either way: Current Block: 64040


---------------------------------------------


1.0.1d - Release: Updates to the UI. Added Immature label. Values of 0 CSD are ommited from the UI. Added Coinbase Rewards to Debug Console, Updated the Difficulty Value to be Current Difficulty. Stability Issues Resolved.

Ubuntu 1.0.1d - Release
Windows 1.0.1d - Release



Thank You,
Viz.
sr. member
Activity: 291
Merit: 250
I would like to suggest for everybody to check their nodes because I think the network was forked. I have 3 main nodes that I'm using for mining and I found all of them on different block height. It looks like just one of them was on the right fork (at the moment of writing on 64030, similar to the pool). One of my wrong node had even 20+ connections.
Jump to: