Pages:
Author

Topic: [ANN] ZERO - fork of Zcash with harder mining params - page 58. (Read 131845 times)

full member
Activity: 235
Merit: 100
New version of Optiminer/Zero for AMD GPUs with 4GB RAM: https://github.com/Optiminer/OptiminerZero/raw/master/optiminer-zero-1.1.0.zip
optiminer, great news for so many smaller miners here.
What did it take to fit into the 4GB, please?
  Tearo
legendary
Activity: 980
Merit: 1001
aka "whocares"
New version of Optiminer/Zero for AMD GPUs with 4GB RAM: https://github.com/Optiminer/OptiminerZero/raw/master/optiminer-zero-1.1.0.zip

I posted this on the other thread, can you make available the 4gb version for Linux.  
answered on the other thread
Thanks
full member
Activity: 187
Merit: 100
full member
Activity: 149
Merit: 100
Volume kicking in - marketcap nearing 200 $ - nice Cool
sr. member
Activity: 1419
Merit: 275
Community built, Privacy driven
Hello
How can I get in to the slack ? Because the link in the first post doesn't work anymore
Is there a website forthcoming ?
thks
Pm me with your email address
newbie
Activity: 14
Merit: 0
Hello
How can I get in to the slack ? Because the link in the first post doesn't work anymore
Is there a website forthcoming ?
thks
full member
Activity: 235
Merit: 100
I had it run on -t3 and I had a few invalid shares, a lot actually, but it seems to be less than 1 sol/s. on a 3 threads on a steamroller quad that gets toasty.
You may be better off running 2 threads at 80% CPU load than say 3 and pegged at 100% and forcing the system to swap all the time and perhaps overheat. Try it...
Your mileage will very.
  Tearo
P.S. Will have an updated set of CPU and GPU results in a week.
member
Activity: 83
Merit: 10
would you happen to know how well it hashes on an i7, say dual vs single channel?
Will be re-doing benchmarking in about two weeks and let you know.
What i7 MB are you using, with what speed memory?
  Tearo
ah, i don't have an i7 just yet but i've been eyeing some upgrades, currently on pretty entry-medium grade cpus. I get about 0.2 sol/s on an AMD quad -t1 but the pool suggests a bit more than that ~3S/s but my guess is it's such a low number the pool can't give a solid estimate. in either case it does get a little unstable and it comes really close to my ram limit, which might be holding it back a bit, i'm going to Frankenstein my parts and have it run on 16gb.
*edit*
I had it run on -t3 and I had a few invalid shares, a lot actually, but it seems to be less than 1 sol/s. on a 3 threads on a steamroller quad that gets toasty.
full member
Activity: 235
Merit: 100
I have no tool to explore the network node numbers. I only tried to analyze how many nodes my node could connect to, and after discovering peers how many of them accepted connections (log shows connect failures).
Hm, anyone can jump in to correct me, but the two hosted nodes that are mentioned via addnode in the .conf file, they are probably reseeding addresses of nodes seen earlier but no longer there?

Right now my VPS node is swamped by another project, but when that's over, will leave a Zero node up in the background.

zerodev2, if it's not too much trouble, could you post a pre-built version of the Windows node on Github? [with all the disclaimers] Don't have the cycles to get into Windows builds right now, but could run one on an available box.
  Tearo
P.S. Kudos on filing a pull request with the Zero Github repo.
full member
Activity: 235
Merit: 100
would you happen to know how well it hashes on an i7, say dual vs single channel?
Will be re-doing benchmarking in about two weeks and let you know.
What i7 MB are you using, with what speed memory?
  Tearo
member
Activity: 83
Merit: 10
Fascinating algo, i'm trying to stop my mind from immediately wondering what VEGA will do with its HBM2 memory, super-wide bus and if half, single, or double precision is the deciding factor with this algorithm.
The Equihash algo is not particularly CPU intensive, and the Blake2 rounds it does, it's all simple integer arithmetic and bit ops. It was picked specifically because of the steep memory curve. So, if you compare architecturally say an i7 with 4 cores against a cutting edge GPU with dozens of cores, the performance does not scale with the number of cores. The GPUs are using super fast memories, but an i7 has a complex cache structure with 6+ MB of on-chip SRAM. So, if we were to pick Equihash parameters, such that four threads would require 8 GB of memory, resulting performance difference may not be huge, given highly optimized implementations tuned to the memory architecture specifics.

These GPU dies are really huge, and that makes them inherently expensive and always leaves room for yield issues. So the best price per Equihash solution has not been fully explored yet. But it's clear that a dedicated ASIC maker would have to compete with the likes of Intel and AMD, for designing complex memory subsystems and accessing volume production in the most advanced semiconductor processes. Good luck with that...
  Tearo



Blockchain Dynamics podcast, which is my fav Altcoin news source, keeps giving our little Zero continued coverage
http://www.blockchaindynamics.net/episode-59-outline.html

It was also mentioned in earlier episodes (55-57). Give it a listen, and you can also thank them for supporting the cause in their forum on Cryptopia
https://www.cryptopia.co.nz/Forum/Thread/634?page=6
Hey, nobody bothered to leave a message for the BD folks, telling them how much we love them and appreciate their coverage of Zero. Wake up and promote the coin, you lazy bums!

would you happen to know how well it hashes on an i7, say dual vs single channel?
full member
Activity: 235
Merit: 100
Fascinating algo, i'm trying to stop my mind from immediately wondering what VEGA will do with its HBM2 memory, super-wide bus and if half, single, or double precision is the deciding factor with this algorithm.
The Equihash algo is not particularly CPU intensive, and the Blake2 rounds it does, it's all simple integer arithmetic and bit ops. It was picked specifically because of the steep memory curve. So, if you compare architecturally say an i7 with 4 cores against a cutting edge GPU with dozens of cores, the performance does not scale with the number of cores. The GPUs are using super fast memories, but an i7 has a complex cache structure with 6+ MB of on-chip SRAM. So, if we were to pick Equihash parameters, such that four threads would require 8 GB of memory, resulting performance difference may not be huge, given highly optimized implementations tuned to the memory architecture specifics.

These GPU dies are really huge, and that makes them inherently expensive and always leaves room for yield issues. So the best price per Equihash solution has not been fully explored yet. But it's clear that a dedicated ASIC maker would have to compete with the likes of Intel and AMD, for designing complex memory subsystems and accessing volume production in the most advanced semiconductor processes. Good luck with that...
  Tearo



Blockchain Dynamics podcast, which is my fav Altcoin news source, keeps giving our little Zero continued coverage
http://www.blockchaindynamics.net/episode-59-outline.html

It was also mentioned in earlier episodes (55-57). Give it a listen, and you can also thank them for supporting the cause in their forum on Cryptopia
https://www.cryptopia.co.nz/Forum/Thread/634?page=6
Hey, nobody bothered to leave a message for the BD folks, telling them how much we love them and appreciate their coverage of Zero. Wake up and promote the coin, you lazy bums!
member
Activity: 83
Merit: 10
Fascinating algo, i'm trying to stop my mind from immediately wondering what VEGA will do with its HBM2 memory, super-wide bus and if half, single, or double precision is the deciding factor with this algorithm. In any case, I can definitely see this coin finding its niche, especially if the novel differences setting it aside from others come into play in a significant or generally positive way.
full member
Activity: 235
Merit: 100
I see on page 1: "faster block verifications 4x"... so what is the target block time?
As the dev said: 2-minute blocks at 10 coins == 7200 coins/day (the same rate as BTC and Zcash before the first halvening)

What he's referring to regarding the 'verification' are the Equihash PoW algorithm parameters. (Google it)
  Tearo

TL:DR
Numerous earlier attempts by various cryptocurrencies to make PoW memory hard did not succeed. The reasoning was to make ASICs impractical and to nerf GPUs, to support wider distribution of mining. Most of the time people talked about the 51% malicious attack, but current Bitcoin fiasco shows that mining consolidation may lead to severe governance problems. And we have discovered that large chunks of hash moving to and from a smaller chains can be disruptive and even predatory.

Zcash went to Equihash exactly due to its promise of being memory hard. However, due to significant community contribution to optimize the CPU but particularly the memory requirements, the parameters that the Zcash team chose initially turned out not to be hard enough to nerf GPUs. And they never found their way to increase them prior to launch, even though the choice was questioned already.

Zcash uses N=200 K=9, which produces a 1364 byte solution. The whole point of this Zero project is to toughen up the parameters, to N=192 K=7.  The resulting PoW solution actually goes down in size to 420 and takes less time to verify, which is great. Meanwhile, the RAM and CPU complexity increases a bunch.

However, even these may not be hard enough, as you can see that the hash is overwhelmingly dominated by the GPU farms and CPU mining is not feasible. Personally, I'd like to test increasing the parameters further. So anyone likewise inclined, do message me. 



Blockchain Dynamics podcast, which is my fav Altcoin news source, keeps giving our little Zero continued coverage
http://www.blockchaindynamics.net/episode-59-outline.html

It was also mentioned in earlier episodes (55-57). Give it a listen, and you can also thank them for supporting the cause in their forum on Cryptopia
https://www.cryptopia.co.nz/Forum/Thread/634?page=6
full member
Activity: 149
Merit: 100
trading volume extremely low Huh
member
Activity: 127
Merit: 10
I see on page 1: "faster block verifications 4x"... so what is the target block time?
full member
Activity: 149
Merit: 100
Glad to see development on this coin, whos going to be taking over the slack?
till we find someone with more tec skills and time i can try  Grin
full member
Activity: 196
Merit: 100
Glad to see development on this coin, whos going to be taking over the slack?
full member
Activity: 149
Merit: 100
I love this project - now we have 2 devs !  Grin
newbie
Activity: 7
Merit: 0
On the topic of the ZERO network, two things are apparent:
1. There are very few running ZERO nodes
2. Very few of those few ZERO nodes accept incoming connections
In fact my own node constantly has only one peer connected. The only node that (seems to) readily accepts connections is 35.164.216.74 (put up by the ZERO creator). In this condition the ZERO network is not really decentralized and resilient at all...
So let us try to fix this! I have started a ZERO node to the "benefit of the community" - IP 94.176.235.178  It accepts incoming connections. Everyone interested may add it to their config. file ~/.zero/zero.conf:
addnode=94.176.235.178
This node is based on the ZERO code-base at: https://github.com/zerodev2/zero
I would ask all those interested in having a strong ZERO network to either run a node that accepts connections or help me run this one (at least) The node costs approx 0.8 USD per day - at the current rate this is 5 ZER. All ZER contributions I receive to this ZERO address
t1L7TfvTQb9B78sLxH9cfx65aBVKfrFJMBQ
will be used to pay for the node... If enough people help with a few pennies - we can keep it running. This should be just a start - one extra node does not make a network ;-)

zerodev2, you are DA MAN!
Can you tell us how to check the state on the network, the number of running nodes, please?
And I'll be sure to leave a Zero node up and running as well.
  Tearo

I have no tool to explore the network node numbers. I only tried to analyze how many nodes my node could connect to, and after discovering peers how many of them accepted connections (log shows connect failures). So what I wrote about the network was not 100% certain but it looks that way...
Pages:
Jump to: