Topbanker
Jr. Member
Offline
Activity: 157
Merit: 1
|
|
July 29, 2015, 10:10:22 PM |
|
yeah, I noticed your account was created mostly for that coin +1, do you want a sticker too? i would love an Axiom sticker!!
|
|
|
|
Fuzzbawls
|
|
July 29, 2015, 10:29:52 PM |
|
I've got a Mac wallet ready to be released, just waiting to hear back from the dev team.
|
|
|
|
seabirds
Member
Offline
Activity: 116
Merit: 10
|
|
July 30, 2015, 12:33:53 AM |
|
buy as you can before late
|
|
|
|
bones261
Legendary
Offline
Activity: 1806
Merit: 1828
|
|
July 30, 2015, 01:08:36 AM |
|
Can someone educate me? I thought AMD GPUs were superior to Nvidia for hashing. However, a cuda miner is out, but I've only heard a brief mention that someone may come out with one for OpenCL, when they have time. Is Cuda easier to program than OpenCL? Just curious.
|
|
|
|
timertrainer
|
|
July 30, 2015, 01:19:18 AM |
|
Please dump some AXIOM, need some more to stake properly.
|
|
|
|
bones261
Legendary
Offline
Activity: 1806
Merit: 1828
|
|
July 30, 2015, 01:29:30 AM |
|
Please dump some AXIOM, need some more to stake properly.
I'm sorry, but my wallet was offline for hours, today. I won't be able to take my courtesy dump this evening.
|
|
|
|
ozboy2014
|
|
July 30, 2015, 01:43:36 AM |
|
Please dump some AXIOM, need some more to stake properly.
how many you need to stake anyway?
|
|
|
|
AxiomCryptocurrency (OP)
Newbie
Offline
Activity: 42
Merit: 0
|
|
July 30, 2015, 01:47:05 AM |
|
The ANN has been updated with a much more coherent Block Rewards Schedule. It is reproduced below for your convenience: Block Rewards Schedule
Proof of Work (POW) Schedule
Blocks 1 - 800 = 500 AXIOM per block Blocks 801 - 1440 = 200 AXIOM per block Blocks 1441 - 5040 = 100 AXIOM per block Blocks 5041 - 9360 = 50 AXIOM per block Blocks 9361 - 13680 = 25 AXIOM per block Blocks 13681 - 18000 = 10 AXIOM per block Blocks 18001 - 156240 = 5 AXIOM per block Blocks 156241 - 160560 = 10 AXIOM per block Blocks 160561 - 164880 = 50 AXIOM per block Blocks 164881 - 169200 = 100 AXIOM per block Blocks 169201 - 173520 = 50 AXIOM per block Blocks 173521 - 177840 = 25 AXIOM per block Blocks 177841 - 182160 = 10 AXIOM per block Blocks 182161 - 707760 = 5 AXIOM per block Blocks 707761 - 1233360 = 2.5 AXIOM per block Blocks 1233361 - 1758960 = 1.25 AXIOM per block Blocks 1758961 - Forever = 1 AXIOM per block
Proof of Stake (POS) Schedule
Blocks 1 - 800 = 200 AXIOM per block Blocks 801 - 1440 = 200 AXIOM per block Blocks 1441 - 5040 = 100 AXIOM per block Blocks 5041 - 9360 = 75 AXIOM per block Blocks 9361 - 13680 = 60 AXIOM per block Blocks 13681 - 18000 = 50 AXIOM per block Blocks 18001 - 156240 = 5 AXIOM per block Blocks 156241 - 160560 = 80 AXIOM per block Blocks 160561 - 164880 = 200 AXIOM per block Blocks 164881 - 169200 = 110 AXIOM per block Blocks 169201 - 173520 = 60 AXIOM per block Blocks 173521 - 177840 = 40 AXIOM per block Blocks 177841 - 182160 = 20 AXIOM per block Blocks 182161- 707760 = 5 AXIOM per block Blocks 707761- 1233360 = 2.5 AXIOM per block Blocks 1233361 - 1758960 = 1.25 AXIOM per block Blocks 1758961 - Forever = 1 AXIOM per block
|
|
|
|
timertrainer
|
|
July 30, 2015, 01:54:05 AM |
|
Please dump some AXIOM, need some more to stake properly.
how many you need to stake anyway? If you don't have enough you won't hit blocks as often.
|
|
|
|
z38630610
Legendary
Offline
Activity: 1050
Merit: 1000
|
|
July 30, 2015, 02:11:43 AM |
|
dev,what time give our use ccminer miner ?
|
|
|
|
mastertrader777
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
July 30, 2015, 02:15:07 AM |
|
Nice clean consolidation. I like it.
im looking at this coin also ... toshidesk include? ... ... #crysx Oh yes, how did you know?
|
|
|
|
dga
|
|
July 30, 2015, 02:15:58 AM |
|
Well, heck - while all of the crypto mining devs are having fun offering toys for sale, how about: 2 BTC for a 15-20% speed boosted version (on my very large test machine, goes from 312 hash/s to 380 hash/sec). x86 specific. Exclusive; it goes to only one person. You get any speedups I make in the next day or so while I keep poking at it, though I don't guarantee results past what I've already got running. PM me first, since I'll only sell this to one person. (Of course, that "one person" can also be "please open source the changes" - or "I will resell it", or "I will share it with my friends". I'm agnostic. I'd love it if you asked me to open source it, really.)
|
|
|
|
timertrainer
|
|
July 30, 2015, 02:18:41 AM |
|
AXIOM developers pinged me to give an opinion on the GPU speedup of the AXIOM PoW function.
I wrote the draft of the paper about RandMemoHash back in 2013, after playing with RandMemoHash a bit. I tested it with a SINGLE GPU (that was even older), and could not get any speedup. My paper does not show any proof, not any real world comparison over several GPU models, so it is definitively unfinished. The suggested parameters are not proven to be valid for all existent GPU models (and less for future models). People should never take for granted what an non-peer-reviewed privately-published draft paper says.
I would have liked that Axiom developers would have pinged me to give an update on it before implementing it.
Having said this, I find that a 5x GPU speedup quite good resistance, considering that a GPU is generally better than a CPU in almost every task. CPUs are good at executing large programs, doing paging, protecting memory, doing I/O. Nothing that a PoW can make use of.
GPU memory system is designed for throughput, and it has generally about 6 times the bandwidth available to a CPU. RandMemoHash bottleneck is the DDR/GDDR memory bus, so that speedup can be expected.
Also you must consider power-usage in the equation: that may make it better or worse for GPU-mining.
I don't know if tweaking the parameters would improve it. Maybe using 8 MB instead of 2 MB can prevent the use of some L2 caches in some boards. But the more space you require, the slower it is to verify the PoW. And this is a cat-and-mouse race, since future models will probably increase the size of the cache.
The Axiom developers & community could collect some real world numbers and try to find an improved parameter set (if it is really needed and if there is a better one).
I wish AXIOM users the best luck.
Sergio.
Wow, straight from the horse's mouth! Thanks a lot for your input Mr. Lerner, I hope we'll see some revolutionary results from AXIOM.
|
|
|
|
chrysophylax
Legendary
Offline
Activity: 2870
Merit: 1091
--- ChainWorks Industries ---
|
|
July 30, 2015, 02:19:10 AM |
|
Well, heck - while all of the crypto mining devs are having fun offering toys for sale, how about: 2 BTC for a 15-20% speed boosted version (on my very large test machine, goes from 312 hash/s to 380 hash/sec). x86 specific. Exclusive; it goes to only one person. You get any speedups I make in the next day or so while I keep poking at it, though I don't guarantee results past what I've already got running. PM me first, since I'll only sell this to one person. hehehe ... maybe i should put the farm up with this also ... ummm ... no - i dont think so ... sp is willing to work on the algo in his fork of ccminer - if anyone is willing to donate ( and obviously if they are interested ) ... #crysx
|
|
|
|
chrysophylax
Legendary
Offline
Activity: 2870
Merit: 1091
--- ChainWorks Industries ---
|
|
July 30, 2015, 02:21:11 AM |
|
AXIOM developers pinged me to give an opinion on the GPU speedup of the AXIOM PoW function.
I wrote the draft of the paper about RandMemoHash back in 2013, after playing with RandMemoHash a bit. I tested it with a SINGLE GPU (that was even older), and could not get any speedup. My paper does not show any proof, not any real world comparison over several GPU models, so it is definitively unfinished. The suggested parameters are not proven to be valid for all existent GPU models (and less for future models). People should never take for granted what an non-peer-reviewed privately-published draft paper says.
I would have liked that Axiom developers would have pinged me to give an update on it before implementing it.
Having said this, I find that a 5x GPU speedup quite good resistance, considering that a GPU is generally better than a CPU in almost every task. CPUs are good at executing large programs, doing paging, protecting memory, doing I/O. Nothing that a PoW can make use of.
GPU memory system is designed for throughput, and it has generally about 6 times the bandwidth available to a CPU. RandMemoHash bottleneck is the DDR/GDDR memory bus, so that speedup can be expected.
Also you must consider power-usage in the equation: that may make it better or worse for GPU-mining.
I don't know if tweaking the parameters would improve it. Maybe using 8 MB instead of 2 MB can prevent the use of some L2 caches in some boards. But the more space you require, the slower it is to verify the PoW. And this is a cat-and-mouse race, since future models will probably increase the size of the cache.
The Axiom developers & community could collect some real world numbers and try to find an improved parameter set (if it is really needed and if there is a better one).
I wish AXIOM users the best luck.
Sergio.
Wow, straight from the horse's mouth! Thanks a lot for your input Mr. Lerner, I hope we'll see some revolutionary results from AXIOM. nice news ... #crysx
|
|
|
|
dga
|
|
July 30, 2015, 02:24:04 AM |
|
Well, heck - while all of the crypto mining devs are having fun offering toys for sale, how about: 2 BTC for a 15-20% speed boosted version (on my very large test machine, goes from 312 hash/s to 380 hash/sec). x86 specific. Exclusive; it goes to only one person. You get any speedups I make in the next day or so while I keep poking at it, though I don't guarantee results past what I've already got running. PM me first, since I'll only sell this to one person. hehehe ... maybe i should put the farm up with this also ... ummm ... no - i dont think so ... sp is willing to work on the algo in his fork of ccminer - if anyone is willing to donate ( and obviously if they are interested ) ... #crysx grin. I was looking at sp_'s code and seeing if I could fix his bug for him and decided it would be better to first play with the (working) CPU miner before I touched the GPU code. Hence this speedup.
|
|
|
|
chrysophylax
Legendary
Offline
Activity: 2870
Merit: 1091
--- ChainWorks Industries ---
|
|
July 30, 2015, 02:38:50 AM |
|
Well, heck - while all of the crypto mining devs are having fun offering toys for sale, how about: 2 BTC for a 15-20% speed boosted version (on my very large test machine, goes from 312 hash/s to 380 hash/sec). x86 specific. Exclusive; it goes to only one person. You get any speedups I make in the next day or so while I keep poking at it, though I don't guarantee results past what I've already got running. PM me first, since I'll only sell this to one person. hehehe ... maybe i should put the farm up with this also ... ummm ... no - i dont think so ... sp is willing to work on the algo in his fork of ccminer - if anyone is willing to donate ( and obviously if they are interested ) ... #crysx grin. I was looking at sp_'s code and seeing if I could fix his bug for him and decided it would be better to first play with the (working) CPU miner before I touched the GPU code. Hence this speedup. i like the speedup - it shows that you have what it takes to get a good optimization done for the algo ... please dont think i was making fun of you ... i really wasnt ... i am just trying ( unsuccessfully obviously ) to point out that if cpu hash increase and optimization is possible - then gpu optimizations will destroy the cpu time and effort you will be putting in ... the speedup is quite substantial - which leads me to believe that there is a LOT that can be done with the algo insofaras optimization is concerned ... though - i could be completely wrong ... #crysx
|
|
|
|
donnyespo
|
|
July 30, 2015, 02:48:43 AM |
|
my wallet just went offline, its been running fine since launch.. Any idea what it could be?
|
|
|
|
dga
|
|
July 30, 2015, 02:52:50 AM |
|
Well, heck - while all of the crypto mining devs are having fun offering toys for sale, how about: 2 BTC for a 15-20% speed boosted version (on my very large test machine, goes from 312 hash/s to 380 hash/sec). x86 specific. Exclusive; it goes to only one person. You get any speedups I make in the next day or so while I keep poking at it, though I don't guarantee results past what I've already got running. PM me first, since I'll only sell this to one person. hehehe ... maybe i should put the farm up with this also ... ummm ... no - i dont think so ... sp is willing to work on the algo in his fork of ccminer - if anyone is willing to donate ( and obviously if they are interested ) ... #crysx grin. I was looking at sp_'s code and seeing if I could fix his bug for him and decided it would be better to first play with the (working) CPU miner before I touched the GPU code. Hence this speedup. i like the speedup - it shows that you have what it takes to get a good optimization done for the algo ... please dont think i was making fun of you ... i really wasnt ... i am just trying ( unsuccessfully obviously ) to point out that if cpu hash increase and optimization is possible - then gpu optimizations will destroy the cpu time and effort you will be putting in ... the speedup is quite substantial - which leads me to believe that there is a LOT that can be done with the algo insofaras optimization is concerned ... though - i could be completely wrong ... #crysx No, no - I was just mentioning why I was looking at it in the first place (because of sp). I could double the speed of the CPU miner again, but it starts to take more work that way. I might do it for fun just to keep the GPU people on their toes, but I may not have time. (Edited to note: Not trying to make a wild claim; that's based upon some profiling and having found a way to circumvent the next big bottleneck. Double is a bit handwavy, of course.)
|
|
|
|
seabirds
Member
Offline
Activity: 116
Merit: 10
|
|
July 30, 2015, 02:54:27 AM |
|
Markets is so quiet
|
|
|
|
|