Nexus - Pure SHA3 + CPU/GPU + nPoS + 15 Active Innovations + More to Come - page 179.

pdogg147

sr. member

Activity: 339

Merit: 266

Advancing Liberty Through Blockchain

Quote from: irwanjabryg on November 25, 2015, 10:56:58 PM

Quote from: pdogg147 on November 25, 2015, 10:06:23 PM

Quote from: merc84 on November 25, 2015, 06:35:43 PM

An update from the dev team would be nice at this point?

Hi All,

Since we recently decided to change the trust key expiration algorithm so trust keys expires in relation to how long your trust key has been active (1 day for every 7 days) rather than a set expiration time (3 days, 7 days, etc), the coding is a little more involved and is taking a little longer. The code will also be updated to reactivate trust keys so those that have lost them will be rewarded on some level. Viz will be on later to give an updated timeline for completion. Sorry for the delay in addressing this.

Thanks,

pdogg147

Dev work hopefully completed soon Cheesy

Yes. I would say weeks not months. As I mentioned Viz will provide a timeline update in the near future. Thanks for your patience.

pdogg147

sr. member

Activity: 339

Merit: 266

Advancing Liberty Through Blockchain

Quote from: merc84 on November 25, 2015, 10:58:42 PM

Quote from: pdogg147 on November 25, 2015, 10:06:23 PM

Quote from: merc84 on November 25, 2015, 06:35:43 PM

An update from the dev team would be nice at this point?

Hi All,

Since we recently decided to change the trust key expiration algorithm so trust keys expires in relation to how long your trust key has been active (1 day for every 7 days) rather than a set expiration time (3 days, 7 days, etc), the coding is a little more involved and is taking a little longer. The code will also be updated to reactivate trust keys so those that have lost them will be rewarded on some level. Viz will be on later to give an updated timeline for completion. Sorry for the delay in addressing this.

Thanks,

pdogg147

Just to clarify is that 1 day per 7 days upto some maximum?

I don't believe we were planning to put a limit on it. Your interest rate will decay as well, but if your key is active for 7 months, it wouldn't completely expire for 1 month.

Wolf0

member

Activity: 81

Merit: 1002

It was only the wind.

Quote from: Supercomputing on November 24, 2015, 05:49:32 PM

@Wolf0

Downloaded from: https://github.com/BitSlapper/SKMiner

Apart from fixing a few bugs and adding some debugging code, I’ve only made a one line change to the OpenCL (sk1024_djm.cl) kernel code.

It would take a few hours to optimize the OpenCL kernel (using CodeXL) to reduce the VGPRs usage thereby increasing the occupancy. But since you’ve already done so and your miner is significantly faster, would you mind sharing your code?

Perhaps when the miner I'm working on for Viz is released. In the meantime, I'll show you my CodeXL analysis for Tahiti if you show me yours for the one you have.

I didn't optimize the existing kernel, really, I rewrote it, but it's surprising that such a small edit would do so well.

merc84

hero member

Activity: 799

Merit: 1000

Quote from: pdogg147 on November 25, 2015, 10:06:23 PM

Quote from: merc84 on November 25, 2015, 06:35:43 PM

An update from the dev team would be nice at this point?

Hi All,

Since we recently decided to change the trust key expiration algorithm so trust keys expires in relation to how long your trust key has been active (1 day for every 7 days) rather than a set expiration time (3 days, 7 days, etc), the coding is a little more involved and is taking a little longer. The code will also be updated to reactivate trust keys so those that have lost them will be rewarded on some level. Viz will be on later to give an updated timeline for completion. Sorry for the delay in addressing this.

Thanks,

pdogg147

Just to clarify is that 1 day per 7 days upto some maximum?

irwanjabryg

hero member

Activity: 980

Merit: 512

Quote from: pdogg147 on November 25, 2015, 10:06:23 PM

Quote from: merc84 on November 25, 2015, 06:35:43 PM

An update from the dev team would be nice at this point?

Hi All,

Since we recently decided to change the trust key expiration algorithm so trust keys expires in relation to how long your trust key has been active (1 day for every 7 days) rather than a set expiration time (3 days, 7 days, etc), the coding is a little more involved and is taking a little longer. The code will also be updated to reactivate trust keys so those that have lost them will be rewarded on some level. Viz will be on later to give an updated timeline for completion. Sorry for the delay in addressing this.

Thanks,

pdogg147

Dev work hopefully completed soon Cheesy

merc84

hero member

Activity: 799

Merit: 1000

Quote from: pdogg147 on November 25, 2015, 10:06:23 PM

Quote from: merc84 on November 25, 2015, 06:35:43 PM

An update from the dev team would be nice at this point?

Hi All,

Since we recently decided to change the trust key expiration algorithm so trust keys expires in relation to how long your trust key has been active (1 day for every 7 days) rather than a set expiration time (3 days, 7 days, etc), the coding is a little more involved and is taking a little longer. The code will also be updated to reactivate trust keys so those that have lost them will be rewarded on some level. Viz will be on later to give an updated timeline for completion. Sorry for the delay in addressing this.

Thanks,

pdogg147

No problems thanks for the update.

Wolf0

member

Activity: 81

Merit: 1002

It was only the wind.

Well, I suppose it doesn't matter - mine is still significantly faster (NSFW): https://ottrbutt.com/miner/nirowolf-11242015.png

pdogg147

sr. member

Activity: 339

Merit: 266

Advancing Liberty Through Blockchain

Quote from: merc84 on November 25, 2015, 06:35:43 PM

An update from the dev team would be nice at this point?

Hi All,

Since we recently decided to change the trust key expiration algorithm so trust keys expires in relation to how long your trust key has been active (1 day for every 7 days) rather than a set expiration time (3 days, 7 days, etc), the coding is a little more involved and is taking a little longer. The code will also be updated to reactivate trust keys so those that have lost them will be rewarded on some level. Viz will be on later to give an updated timeline for completion. Sorry for the delay in addressing this.

Thanks,

pdogg147

merc84

hero member

Activity: 799

Merit: 1000

An update from the dev team would be nice at this point?

Wolf0

member

Activity: 81

Merit: 1002

It was only the wind.

Quote from: Supercomputing on November 24, 2015, 04:19:36 PM

Miner version: 1.2 (cleaned up to compile and run on Linux)
OS: Ubuntu 14.04 LTS
Driver: 14.9
GPU: R9 280X (stock)

[MASTER] Coinshield Network: New Block 511517
39.5 MH/s | 0 Blks ACC=0 REJ=0 | Height = 511517 | Diff = 37 0-bits | 00:29:00
39.5 MH/s | 0 Blks ACC=0 REJ=0 | Height = 511517 | Diff = 37 0-bits | 00:29:11
39.6 MH/s | 0 Blks ACC=0 REJ=0 | Height = 511517 | Diff = 37 0-bits | 00:29:22

[Block Nonce = 989773809]
00000000035f7878e09d8e2c442be919182bf0f6caed9b14e2ef1252e40b6925f30bfed7aa6c70\
e444fba536bd560b643886ca5a83fe35d453367bfc1c0c687cee6d815eeab873cfea8acdd2b887\
9560e8b8fa81c1339c1bff614ac7113abdac2085c684582845cfca6728eb848709e7d77411e141\
a6126122709105b5da1cda

******* BLOCK with 38 Leading Zero Bits FOUND *******

...Preparing for Block Submission...

Submitting Block...
[MASTER] Block Accepted By Coinshield Network.
[MASTER] Coinshield Network: New Block 511518
39.3 MH/s | 1 Blks ACC=1 REJ=0 | Height = 511518 | Diff = 37 0-bits | 00:29:34
39.3 MH/s | 1 Blks ACC=1 REJ=0 | Height = 511518 | Diff = 37 0-bits | 00:29:45

That one isn't for download on the site. Where is it?

irwanjabryg

hero member

Activity: 980

Merit: 512

Quote from: ukon on November 25, 2015, 06:13:19 AM

Quote from: irwanjabryg on November 25, 2015, 06:09:13 AM

Quote from: ukon on November 25, 2015, 06:04:50 AM

Quote from: irwanjabryg on November 25, 2015, 05:59:49 AM

Quote from: ukon on November 25, 2015, 05:57:24 AM

Quote from: nara1892 on November 24, 2015, 09:39:23 PM

waiting for wallet and add on polo Roll Eyes

already 3 weeks of no movement..

kimcil ohh uyeahh Shocked

Soon the price will go 2k sats

I will buy if the price of 3 kimcil Niro to 2k SATS Wink

niro hope Able to penetrate 2k ..
to buy kimcil.. Cry

But is it possible ? 2k so far , Is Dev was able to keep its promise to improve the quality Niro ?

dev certainly capable and kept his promise
because the dev has power kimcil..

I look forward to it , because it is important for public confidence of shareholders , I had to wait about three months for this moment Cheesy

ukon

sr. member

Activity: 336

Merit: 250

SPYCE | Rise of Web 3.0 - www.decenternet.com

Quote from: irwanjabryg on November 25, 2015, 06:09:13 AM

Quote from: ukon on November 25, 2015, 06:04:50 AM

Quote from: irwanjabryg on November 25, 2015, 05:59:49 AM

Quote from: ukon on November 25, 2015, 05:57:24 AM

Quote from: nara1892 on November 24, 2015, 09:39:23 PM

waiting for wallet and add on polo Roll Eyes

already 3 weeks of no movement..

kimcil ohh uyeahh Shocked

Soon the price will go 2k sats

I will buy if the price of 3 kimcil Niro to 2k SATS Wink

niro hope Able to penetrate 2k ..
to buy kimcil.. Cry

But is it possible ? 2k so far , Is Dev was able to keep its promise to improve the quality Niro ?

dev certainly capable and kept his promise
because the dev has power kimcil..

Wolf0

member

Activity: 81

Merit: 1002

It was only the wind.

Quote from: merc84 on November 24, 2015, 03:40:11 PM

Honestly can't remember if its default.

"algorithm" : "sk1024_djm",
   "gpu-engine" : "1100",
   "gpu-memclock" : "1250",
   "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" : "256",

Close enough to it. I don't get it. Unless you have 290X cards.

irwanjabryg

hero member

Activity: 980

Merit: 512