Search content
Sort by
Showing 20 of 46 results by almonk
Re: 8th Alt coin thread. Or what to do now that asics are all over the place.
AMD GPUs consume a lot more power for the same hashrate on compute heavy algos.
I am not too technical on the details but what is the deal exactly with ProgPOW? It seems that it will level the field with ASICs and GPUs however the brand of GPU seems to play a factor.
It seems that Nvidia performs much better than AMD, and is the reason for this that Nvidia generally costs more and since it costs more they want to make it more fair in that regards.
For example, say you can buy 2 AMDs for the price of 1 Nvidia. The 1 Nvidia will perform at the exact same speed as the 2 AMDs combined. Is this the point they are going for or is it just the way that the current miners are optimized?
It seems that Nvidia performs much better than AMD, and is the reason for this that Nvidia generally costs more and since it costs more they want to make it more fair in that regards.
For example, say you can buy 2 AMDs for the price of 1 Nvidia. The 1 Nvidia will perform at the exact same speed as the 2 AMDs combined. Is this the point they are going for or is it just the way that the current miners are optimized?
Re: [ANN] BEAM | Mimblewimble | Private | Scalable | No ICO | No Pre Mine
Or somebody put FPGAs to work..
If the price doesn't go up on Beam coin, Its not going to be worth mining anymore. I think in an effort to exclude ASIC's, somebody forgot about the HUGE GPU farms out there. 
Re: 8th Alt coin thread. Or what to do now that asics are all over the place.
Yeah, it can be some FPGAs..
XMR after the CNV8 fork was not that profitable as before.
XMR after the CNV8 fork was not that profitable as before.
anyone else notice the sudden diff jump in XMR.... Might be a hint.... Price surely isn't reflecting it; so it must be a new machine at play. I highly doubt that much gear was turned on all at once based on any other reasoning....
Re: [ANN] PYRITE | $PYE | POW/POS HYBRID | SHA256Q | FAIR LAUNCH | NO PREMINE | GPU
Some stats for AMD mining:
AMD RX 480/580 ~400MH/s
AMD RX 460 ~150MH/s
You need to increase core clocks and find your best hashrate/watt ratio.
AMD RX 480/580 ~400MH/s
AMD RX 460 ~150MH/s
You need to increase core clocks and find your best hashrate/watt ratio.
I've got the pool working good now, but trying to solo is still giving my HW errors. I'm using the default .bat file, just changing the pool and port to local wallet. And of course my user name and password. Windows 10, 18.6 drivers, vega 64s.
Can you post your command line arguments how you are trying to run it? Also is it on linux or windows and the drivers version.
I'm getting HW errors on both solo and pool. They go away if I drop the intensity way down, but then I'm only getting about 3MHs per vega. My 1070's are running 450MH with ccminer.
Re: [ANN] PYRITE | $PYE | POW/POS HYBRID | SHA256Q | FAIR LAUNCH | NO PREMINE | GPU
That sgminer fork does not support solo mining at this moment. Just stay with pool or set up your own pool.
I've got the pool working good now, but trying to solo is still giving my HW errors. I'm using the default .bat file, just changing the pool and port to local wallet. And of course my user name and password. Windows 10, 18.6 drivers, vega 64s.
Can you post your command line arguments how you are trying to run it? Also is it on linux or windows and the drivers version.
I'm getting HW errors on both solo and pool. They go away if I drop the intensity way down, but then I'm only getting about 3MHs per vega. My 1070's are running 450MH with ccminer.
Re: [ANN] PYRITE | $PYE | POW/POS HYBRID | SHA256Q | FAIR LAUNCH | NO PREMINE | GPU
Can you post your command line arguments how you are trying to run it? Also is it on linux or windows and the drivers version.
I'm getting HW errors on both solo and pool. They go away if I drop the intensity way down, but then I'm only getting about 3MHs per vega. My 1070's are running 450MH with ccminer.
Re: [ANN] PYRITE | $PYE | POW/POS HYBRID | SHA256Q | FAIR LAUNCH | NO PREMINE | GPU
Are you trying to solo mine or pool?
Anyone else getting HW errors on AMD miner? Any fix?
Re: [ANN] PYRITE | $PYE | POW/POS HYBRID | SHA256Q | FAIR LAUNCH | NO PREMINE | GPU
I just made windows build for AMD mining software.
https://github.com/almonk5/sgminer-sha256q/releases/download/0.1/sgminer-sha256q-bin-cygwin.zip
Try it out.
https://github.com/almonk5/sgminer-sha256q/releases/download/0.1/sgminer-sha256q-bin-cygwin.zip
Try it out.
Re: 8th Alt coin thread. Or what to do now that asics are all over the place.
Some PoS implementations use limited time range let's say +-10 minutes in unix time seconds from time now as limited variable input into hash function. Something like nonce in PoW but in PoW nonce usually is not very strictly limited.
POS requires a coin value to be staked on the network (locked in). I speak of POW.
This is about strictly adding a timebase standard that can be used to effectively nullify things that will calculate above a certain speed. IT would make all devices effectively equal at a point; and would boil down to quantity of devices from that point on.... Equal opportunity in a manner of speaking.
of course things like; adding simple functions that salt the time function's process on the next round; they come from the previous round's block's values; and could be beneficial as well.
Isn't it how PoS systems work now?
If a hardware hashing device was based around a 10Mhz oven controlled crystal oscillator; and the algorithm has a time factor built in that can be related/based on this; it could easily become a standard for limiting hashing speeds; and could easily be re-verified as to be a valid result by the network using that time-base schism. It is of-course more involved than just a simple single function; but if worked properly; the time function can be integrated at steps throughout the process of calculating.
Example: Calculate for a result; and during each mathematical operation; do a math operation on the intermediate value/variable with the timer's current value as a salt; do the next step; salt, etc. All salt is based on the timer.
This way; you are forced to conform to the 10Mhz oscillator's salt, and it will disrupt your ability to hash faster as your result won't match someone else that is running the correct timebase, when you are accelerated and hashing faster.
If a hardware hashing device was based around a 10Mhz oven controlled crystal oscillator; and the algorithm has a time factor built in that can be related/based on this; it could easily become a standard for limiting hashing speeds; and could easily be re-verified as to be a valid result by the network using that time-base schism. It is of-course more involved than just a simple single function; but if worked properly; the time function can be integrated at steps throughout the process of calculating.
Example: Calculate for a result; and during each mathematical operation; do a math operation on the intermediate value/variable with the timer's current value as a salt; do the next step; salt, etc. All salt is based on the timer.
This way; you are forced to conform to the 10Mhz oscillator's salt, and it will disrupt your ability to hash faster as your result won't match someone else that is running the correct timebase, when you are accelerated and hashing faster.
POS requires a coin value to be staked on the network (locked in). I speak of POW.
This is about strictly adding a timebase standard that can be used to effectively nullify things that will calculate above a certain speed. IT would make all devices effectively equal at a point; and would boil down to quantity of devices from that point on.... Equal opportunity in a manner of speaking.
of course things like; adding simple functions that salt the time function's process on the next round; they come from the previous round's block's values; and could be beneficial as well.
And it cannot be limited too, because there's nothing stopping miners from mining to multiple address on the same device, using the same range of nonces.
It is probably possible to tie to the amount of coins per each address. Limit available search space to the amount of coins per address. Till the next block.
Re: 8th Alt coin thread. Or what to do now that asics are all over the place.
Some PoS implementations use limited time range let's say +-10 minutes in unix time seconds from time now as limited variable input into hash function. Something like nonce in PoW but in PoW nonce usually is not very strictly limited.
POS requires a coin value to be staked on the network (locked in). I speak of POW.
This is about strictly adding a timebase standard that can be used to effectively nullify things that will calculate above a certain speed. IT would make all devices effectively equal at a point; and would boil down to quantity of devices from that point on.... Equal opportunity in a manner of speaking.
of course things like; adding simple functions that salt the time function's process on the next round; they come from the previous round's block's values; and could be beneficial as well.
Isn't it how PoS systems work now?
If a hardware hashing device was based around a 10Mhz oven controlled crystal oscillator; and the algorithm has a time factor built in that can be related/based on this; it could easily become a standard for limiting hashing speeds; and could easily be re-verified as to be a valid result by the network using that time-base schism. It is of-course more involved than just a simple single function; but if worked properly; the time function can be integrated at steps throughout the process of calculating.
Example: Calculate for a result; and during each mathematical operation; do a math operation on the intermediate value/variable with the timer's current value as a salt; do the next step; salt, etc. All salt is based on the timer.
This way; you are forced to conform to the 10Mhz oscillator's salt, and it will disrupt your ability to hash faster as your result won't match someone else that is running the correct timebase, when you are accelerated and hashing faster.
If a hardware hashing device was based around a 10Mhz oven controlled crystal oscillator; and the algorithm has a time factor built in that can be related/based on this; it could easily become a standard for limiting hashing speeds; and could easily be re-verified as to be a valid result by the network using that time-base schism. It is of-course more involved than just a simple single function; but if worked properly; the time function can be integrated at steps throughout the process of calculating.
Example: Calculate for a result; and during each mathematical operation; do a math operation on the intermediate value/variable with the timer's current value as a salt; do the next step; salt, etc. All salt is based on the timer.
This way; you are forced to conform to the 10Mhz oscillator's salt, and it will disrupt your ability to hash faster as your result won't match someone else that is running the correct timebase, when you are accelerated and hashing faster.
POS requires a coin value to be staked on the network (locked in). I speak of POW.
This is about strictly adding a timebase standard that can be used to effectively nullify things that will calculate above a certain speed. IT would make all devices effectively equal at a point; and would boil down to quantity of devices from that point on.... Equal opportunity in a manner of speaking.
of course things like; adding simple functions that salt the time function's process on the next round; they come from the previous round's block's values; and could be beneficial as well.
Re: 8th Alt coin thread. Or what to do now that asics are all over the place.
Isn't it how PoS systems work now?
If a hardware hashing device was based around a 10Mhz oven controlled crystal oscillator; and the algorithm has a time factor built in that can be related/based on this; it could easily become a standard for limiting hashing speeds; and could easily be re-verified as to be a valid result by the network using that time-base schism. It is of-course more involved than just a simple single function; but if worked properly; the time function can be integrated at steps throughout the process of calculating.
Example: Calculate for a result; and during each mathematical operation; do a math operation on the intermediate value/variable with the timer's current value as a salt; do the next step; salt, etc. All salt is based on the timer.
This way; you are forced to conform to the 10Mhz oscillator's salt, and it will disrupt your ability to hash faster as your result won't match someone else that is running the correct timebase, when you are accelerated and hashing faster.
If a hardware hashing device was based around a 10Mhz oven controlled crystal oscillator; and the algorithm has a time factor built in that can be related/based on this; it could easily become a standard for limiting hashing speeds; and could easily be re-verified as to be a valid result by the network using that time-base schism. It is of-course more involved than just a simple single function; but if worked properly; the time function can be integrated at steps throughout the process of calculating.
Example: Calculate for a result; and during each mathematical operation; do a math operation on the intermediate value/variable with the timer's current value as a salt; do the next step; salt, etc. All salt is based on the timer.
This way; you are forced to conform to the 10Mhz oscillator's salt, and it will disrupt your ability to hash faster as your result won't match someone else that is running the correct timebase, when you are accelerated and hashing faster.
In terms of power supply capacity it is always better have more powerful power supply. If you run it right on the edge you may experience that it may shut down itself from time to time under different environment conditions. Also if you switch to different algos you may find that it may not be enough power and then you will have to rebuild the rig or limit your power usage.
Re: [ANN] PYRITE | $PYE | POW/POS HYBRID | SHA256Q | FAIR LAUNCH | NO PREMINE | GPU
I made SHA256Q miner for AMD GPUs and finally was able to find some time to upload it. You can download it from here https://github.com/almonk5/sgminer-sha256q
Even if you get IP address of the miners, what are going to do with it? ISPs will not give you contact or location info for that IP without court order. You can try to go to your local authorities.