[ANN] [SKC] Skeincoin 0.9.3.1 | Skein-SHA2

[Dosmas]

nice:0

[1713970794]

1713970794

[1713970794]

1713970794

[1713970794]

1713970794

[Red Kendra]

AuxPow has been reverted for the time being while we investigate an issue.

Please use the 0.8.99.13 wallet (see OP) or the latest version from Github.

Thanks

[feeleep]

guys - need active nodes because pool wallet cannot synchronize now

[Red Kendra]

guys - need active nodes because pool wallet cannot synchronize now

195.93.239.31
107.170.194.193

[BlueDragon747]

...

I'm offering a 10k skc bounty on an opensource FPGA implementation of the skein algo.

HW Testing shows that I can get about 2.5MH/s (for the sha256/skein algo) out of a Cyclone IV E115.  Not impressive.  That's only burning about 1W though, so that's 2.5MH/s/W which is kinda "cool" if you're gonna make a large rig of dozens of FPGAs.  With my rig, once I get the stratum proxy working, I'm expecting around 180MH/s for myr-skein.  That's about what you'd expect from a single modern GPU ... meh.

Disappointment.

This still will yield about 5x what my rig is yielding today running the scrypt algo though.  ASICs are starting to kick my ass in the Scrypt realm.  Todays cryptocurrency landscape doesn't appear to have much room left for FPGAs.  The algo's are a whole generation newer (and more complex) than they were in BitCoin days and those damned GPUs are REALLY REALLY fast now!  Even though GPUs are not running algo steps in parallel (like an FPGA can) they're running their core at some insane GHz speed that more than makes up for it.  If I really work at timing issues I can get logic steps in the FPGA to run up to 100MHz.  That's roughly the theoretical max for how fast a single fully unrolled instance of an algo machine can run in this FPGA.  The SHA3 generation of algos though are so much more complex than SHA2 that you'd never fit an entire fully unrolled instance in a single IC.  You have to start making trade offs to shrink the logic into something that will fit and this means increasing the number of clocks per hash.  I've run out of steam at 64 clocks per hash for Skein.

Quite a learning experience

not all of the SHA-3 candidates are more complex some are quite simple by design and work well on FPGA most of the issue are in the IDE and getting it to PAR(ISE is such a pita to use) and high fmax is more luck than any thing else  

I have some 28nm Cyclone v FPGA's here will port blake to them once I have finished some other work I do prefer working in Quartus over ISE  

hashrate wise FPGA is not going to beat GPU but it will use less power which for me here in UK is an important factor to mining

AuxPow has been reverted for the time being while we investigate an issue.

Please use the 0.8.99.13 wallet (see OP) or the latest version from Github.

Thanks

I found with AuxPoW that the block start code had issues as it seems that the AuxPoW blocks start before the check 

hope that helps 

[chiguireitor]

...

I'm offering a 10k skc bounty on an opensource FPGA implementation of the skein algo.

HW Testing shows that I can get about 2.5MH/s (for the sha256/skein algo) out of a Cyclone IV E115.  Not impressive.  That's only burning about 1W though, so that's 2.5MH/s/W which is kinda "cool" if you're gonna make a large rig of dozens of FPGAs.  With my rig, once I get the stratum proxy working, I'm expecting around 180MH/s for myr-skein.  That's about what you'd expect from a single modern GPU ... meh.

Disappointment.

This still will yield about 5x what my rig is yielding today running the scrypt algo though.  ASICs are starting to kick my ass in the Scrypt realm.  Todays cryptocurrency landscape doesn't appear to have much room left for FPGAs.  The algo's are a whole generation newer (and more complex) than they were in BitCoin days and those damned GPUs are REALLY REALLY fast now!  Even though GPUs are not running algo steps in parallel (like an FPGA can) they're running their core at some insane GHz speed that more than makes up for it.  If I really work at timing issues I can get logic steps in the FPGA to run up to 100MHz.  That's roughly the theoretical max for how fast a single fully unrolled instance of an algo machine can run in this FPGA.  The SHA3 generation of algos though are so much more complex than SHA2 that you'd never fit an entire fully unrolled instance in a single IC.  You have to start making trade offs to shrink the logic into something that will fit and this means increasing the number of clocks per hash.  I've run out of steam at 64 clocks per hash for Skein.

Quite a learning experience

not all of the SHA-3 candidates are more complex some are quite simple by design and work well on FPGA most of the issue are in the IDE and getting it to PAR(ISE is such a pita to use) and high fmax is more luck than any thing else  

I have some 28nm Cyclone v FPGA's here will port blake to them once I have finished some other work I do prefer working in Quartus over ISE  

hashrate wise FPGA is not going to beat GPU but it will use less power which for me here in UK is an important factor to mining

AuxPow has been reverted for the time being while we investigate an issue.

Please use the 0.8.99.13 wallet (see OP) or the latest version from Github.

Thanks

I found with AuxPoW that the block start code had issues as it seems that the AuxPoW blocks start before the check 

hope that helps 

Hehe blue on the SKC thread! Cool!

Indeed, Blake is a very simple SHA3 finalist, and it seems Skein is also very simple because it boils down to a tweaked threefish cipher (which is already FPGA fit).

[sheepman]

Just bought me some skein socks from cryptosocks.com 

[chiguireitor]

Just bought me some skein socks from cryptosocks.com 

Have 15 myself, comfortable as can be!

[sheepman]

Anyone know when we are moving forward with the merged mining?

[bolvan]

0.8.99.14 does not sync after 8-NOV. Added all recommended addnodes

[gielbier]

0.8.99.14 does not sync after 8-NOV. Added all recommended addnodes

Do not use 0.8.99.14! (It's the merged version, that got a rollback, because the pools didn't update in time)
Use 0.8.99.13 or 0.8.99.15.

[bolvan]

0.8.99.14 does not sync after 8-NOV. Added all recommended addnodes

Do not use 0.8.99.14! (It's the merged version, that got a rollback, because the pools didn't update in time)
Use 0.8.99.13 or 0.8.99.15.

Then why not to correct the link on skeincoin.org ?

[gielbier]

0.8.99.14 does not sync after 8-NOV. Added all recommended addnodes

Do not use 0.8.99.14! (It's the merged version, that got a rollback, because the pools didn't update in time)
Use 0.8.99.13 or 0.8.99.15.

Then why not to correct the link on skeincoin.org ?

The skeincoin.org version is 0.8.99.13. (skeincoinwin089913.zip) That's the one you need.

[depboy]

What's the chance of SKC having another crack at forking to auxPoW anytime soon?

[Dosmas]

i'dd say work in progress

[gielbier]

Kendra, any update on if or when a new merged mining attempt will be made?

[gielbier]

Definitely a good idea. 

[Dosmas]

What can we do to get this coin really going? I'm looking for ideas and opinions people

I'm thinking a half.com-like site where everything is denominated in SKC. Preferably something with as little centralization as possible.

Anyone else think this is a good idea?

Yes absolutely!Im positive about it.

[gielbier]

Because ppl really seem to like jpgs on ideas and concepts, instead of seeing the real deal.


I will add some screenshots of the app later tonight.

[gielbier]

Clearly ppl can't take a joke.
- Puts up fuggly jpg
- Hashrate drops.

I am not joking on matchtracking. It's real, and it needs testing.