Search content
Sort by
Showing 15 of 15 results by albertlee81
WOOF COIN
Since the beginning of the pandemic, pet surrendering rates have increased dramatically around the world. Waitlists for surrendering household pets have increased to a remarkable eight months as animal shelters and welfare organisations have seen an increase of 34% for animals needing help.
Typically, animal shelters are under resourced and under financed; relying heavily on donations and the volunteer efforts to assist animals.
This is where Woof Coin steps in. As avid lovers of dogs, we wanted to make a difference. Using the power of Proof of Work mining, weâve created a coin where miners are contributing to the donation of money to animal welfare shelters. These shelters initially include the ASPCA who already have a cryptocurrency donation mechanism but with intention to expand to the RSPCA and other organizations suggested by the community.
Our aim is to put animals first and we intend on developing ongoing relationships with pet shelters to help adoption.
Coins Specifications
21 billion supply
Block 2,100,000 halving (4 years estimated)
Algorithm: KawPOW
Proof of Work
Download Links:
https://github.com/WoofCoinMain/WoofCoin/releases/download/WoofCoin/WoofCoin.zip
Social
Coming soon!
Please reach out if you have any questions Smiley
Re: SRBMiner Cryptonight AMD GPU Miner V1.6.9 - native algo switching
Hi.
Please, help me to understand the values of intensity parameter... (I'am trying to get maximum hashrate without HW errors)
In other miners it's calculated from the number of shaders, but there is a results such as 768, 896, etc.. In SRBMiner there is some values between 1-300. How they are correlated with the standart values? For example, intensity of 58 = ??
And what formula I should use for calculations, if I know mem size and number of shaders?
Maybe, someone can share their "intensity" and "worksize" settings for RX560, RX570/580? (interested in normal and heavy/haven algos)
Also, is there any way to get per-card statistics in SRBMiner? Accepted, rejected, HW errors...
Will be gratefull for help.
Please, help me to understand the values of intensity parameter... (I'am trying to get maximum hashrate without HW errors)
In other miners it's calculated from the number of shaders, but there is a results such as 768, 896, etc.. In SRBMiner there is some values between 1-300. How they are correlated with the standart values? For example, intensity of 58 = ??
And what formula I should use for calculations, if I know mem size and number of shaders?
Maybe, someone can share their "intensity" and "worksize" settings for RX560, RX570/580? (interested in normal and heavy/haven algos)
Also, is there any way to get per-card statistics in SRBMiner? Accepted, rejected, HW errors...
Will be gratefull for help.
XMR Stak Intensity is 16 times the SRB intensity. So SRB Intensity of 56 is 896 on stak. They don't work exactly the same so try different numbers for yourself
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s
I still have hashrate droops with the 0.33b6.
One has just occurs on my RX 570 4G after two hours of mining CN V8: from 1100 to 965 h/s.
It's the same hashrate droop I had with the b4 and b5 versions.
I fixed drops on CN-Heavy (and related) only. If i have good feedbacks about it, so i'll put it on V8 too.One has just occurs on my RX 570 4G after two hours of mining CN V8: from 1100 to 965 h/s.
It's the same hashrate droop I had with the b4 and b5 versions.
Hashrate is stable for me on the new version so this is my good feedback. One thing I noticed is that I get better results when I disable and reenable GPUs either using Device Manager or devcon.exe before starting JCE miner on both my RX580 8GBs and RX Vega 56s
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s
Dunno if it's of any help to fix unstable hashrate but I settled on this config for rx570 4gb (880-910 per card).
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":448 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":448 },
And the same but multihash 992 gives me 1830-1870 from vega56. 11.1kh from 6 gpu rig. 1014watts. That rig has been working for 24 hours and hashrate drop was insignificant (10.9kh). But the other rx vega rig works best with multihash 960. I may be wrong but looks like both threads have to have equal multihash and that was not the case in the previous versions.
Big thanks for this great miner!
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":448 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":448 },
And the same but multihash 992 gives me 1830-1870 from vega56. 11.1kh from 6 gpu rig. 1014watts. That rig has been working for 24 hours and hashrate drop was insignificant (10.9kh). But the other rx vega rig works best with multihash 960. I may be wrong but looks like both threads have to have equal multihash and that was not the case in the previous versions.
Big thanks for this great miner!
992/992 is working great on my vega 56s!
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s
I won't comment about the speed, happy if you got it better, but about the settings: Cast, SRB, TeamRed and JCE are close source miners, with different code each. We obviously don't use the reference code (the one of XMRig/stak). So we have each our own best settings, and we don't even use the same units, SRB intensity setting (a number somewhere between 0 and ~100) is unlike my multi_hash which is often arount 500, 1000 or 2000, alpha and beta. For each miner, take time to tune, even between two revisions of same miner.
On GitHub I often get tickets from people who complain they cannot apply one-to-one their xmrstak config. I don't know how and where to say we're two unrelated software
0.33b6 done, now testing. Planned fixes:
On GitHub I often get tickets from people who complain they cannot apply one-to-one their xmrstak config. I don't know how and where to say we're two unrelated software
0.33b6 done, now testing. Planned fixes:
Quote
OpenCL O-2.10 bug solved
More stable hashrate
Little perf boost on all algos ~0.15%
Temperature Watchdog (AMD GPUs only)
More stable hashrate
Little perf boost on all algos ~0.15%
Temperature Watchdog (AMD GPUs only)
First of all, fantastic miner!
What I noticed very quickly was that JCE multihash figures are very similar to intensity figures shared by XMR-Stak and XMRig. When comparing SRB to them, I noticed that SRB intensity is 1/16th of what the open source miners are. By adapting SRB, I took the numbers I used and multiplied them by 16 and the miners seem to go ok. The number I couldn't use though was worksize 9. When I do that, JCE insists that multi_hash be divisible by 16 and by the worksize 9. If it could have been one or the other, I could experiment more. No worries if you want to leave it the way it is. Tuning is just a bit of a hobby of mine
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s
http://json.org/
0.33b6 to be released in less than one day, with the OpenCL bug O.2.10 fixed.
Quote
ws
""
'0009' ws
'000a' ws
'000d' ws
'0020' ws
""
'0009' ws
'000a' ws
'000d' ws
'0020' ws
Quote
Whitespace can be inserted between any pair of tokens.
So my JSON is conformant, and said differently, JSON do'nt care about blankspaces and indentation.0.33b6 to be released in less than one day, with the OpenCL bug O.2.10 fixed.
My Vega56 rig is doing much better than it was on SRB. I had to adapt some of the settings I was using on SRB to JCE to get the most hash (per GPU, 1 thread with 1008 multi_hash and 1 thread with 880 multi_hash)
My RX580 8GBs are par for the course compared to SRB no matter what I tried but I'm still using JCE because I like the effective hash stat
Re: [JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s
Maybe you forgot that the 2+% fee is only for heavy algo and heavy based algos. For v8 and all other algos based on v7 or v8 fee is still 0.9%.
The 2.5% fee is applied to CN Saber too.
CN Saber is a heavy based algo. It has a 4 MB scratchpad, same as Heavy and Haven
It seem this miner does not support passing args through cli. It instead require a config file?
On the bottom of the first post, there are some command line arguments. Pool info through cli is a recent addition if you have an old version
In the future, you can have devfee mining point to a proxy the way XMRIG folks do it
github /xmrig/xmrig-proxy
github /xmrig/xmrig-proxy
V1.5.8
- Fixed a bug in pool switching process
- Fixed a bug in watchdog's "reboot_script"
- Changed default devfee pool for Heavy algo
+ I would like to politely ask everyone if they appreciate my work, to switch their miners to this new version.
The default devfee pool for heavy algo was pool.sumokoin.com, which is under the control of the origin Sumo team.
They self-decided, without any community voting or anything to switch their algo back to now ASIC friendly Cryptonight from block 137500.
That will happen in about two days.
What this means to users of SRBMiner/Me ? On previous versions if you mine any coin on 'heavy' algo from monday, the devfee will connect to pool.sumokoin.com using 'heavy' algo,
but the pool will be using classic CN, so shares will be ALL rejected, and i won't be getting the 0.85% fee.
Thank you in advance, if you are going to support me and going to switch to this version.
- Fixed a bug in pool switching process
- Fixed a bug in watchdog's "reboot_script"
- Changed default devfee pool for Heavy algo
+ I would like to politely ask everyone if they appreciate my work, to switch their miners to this new version.
The default devfee pool for heavy algo was pool.sumokoin.com, which is under the control of the origin Sumo team.
They self-decided, without any community voting or anything to switch their algo back to now ASIC friendly Cryptonight from block 137500.
That will happen in about two days.
What this means to users of SRBMiner/Me ? On previous versions if you mine any coin on 'heavy' algo from monday, the devfee will connect to pool.sumokoin.com using 'heavy' algo,
but the pool will be using classic CN, so shares will be ALL rejected, and i won't be getting the 0.85% fee.
Thank you in advance, if you are going to support me and going to switch to this version.
@doktor83 I'm pretty sure that you are aware of all these occasions, I mean with the hashdrop.
Cards with 4gb memory dont have this issue, at least to me. They reach maximum hashspeed immediately.
The problem is with the 8gb cards.
Whenever I start your miner one of them, sometimes more, can go up to maximum, others no and they stay low all the time
even after 2,3,4 hours of mining.
Next time I'm starting your miner some other cards or card do the opposite thing. It's a random situation.
To help things out, you of course the developer of a great miner to me, I found out that running GPU-Z at the time your miner runs
and passing throu all cards one by one and then exiting, voula all cards running full speed. Problem solved.
But of course this is not a solution!!!
Maybe something with the interrupts?
I'm trying to help!
Cards with 4gb memory dont have this issue, at least to me. They reach maximum hashspeed immediately.
The problem is with the 8gb cards.
Whenever I start your miner one of them, sometimes more, can go up to maximum, others no and they stay low all the time
even after 2,3,4 hours of mining.
Next time I'm starting your miner some other cards or card do the opposite thing. It's a random situation.
To help things out, you of course the developer of a great miner to me, I found out that running GPU-Z at the time your miner runs
and passing throu all cards one by one and then exiting, voula all cards running full speed. Problem solved.
But of course this is not a solution!!!
Maybe something with the interrupts?
I'm trying to help!
On my Vega 56 on 18.3.4 drivers (HCC disabled), I run cast_xmr with the maxmem option and then when the hash rate gets a little higher than 1325, I quit and switch to SRB miner (56 intensity, 8 worksize) and then I get the 1450-1500 hashes
Some people have reported that if you do this with 60 intensity and then drop it back down to 56, you get the full hashrate but I haven't gotten it to work
When I had blockchain drivers, I couldn't get this to work reliably but I did succeed a few times by enabling HCC memory
Very bad: Vega 64 Cryptonight V7
[2018-04-23 23:25:53] Pool accepted result 0x000059B4
[2018-04-23 23:25:55] Pool accepted result 0x000044B1
[2018-04-23 23:25:55] Pool difficulty: 50625
[2018-04-23 23:25:55] Pool sent a new job (ID: 119620357058010)
[2018-04-23 23:25:58] Pool accepted result 0x0000EC14
[2018-04-23 23:26:03] Pool sent a new job (ID: 133028621855191)
[2018-04-23 23:26:11] GPU0: 1494.0 H/S [T: 51c, RPM: 3446, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU1: 1493.0 H/S [T: 51c, RPM: 3772, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU2: 1498.0 H/S [T: 48c, RPM: 3253, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU3: 1493.0 H/S [T: 47c, RPM: 3544, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU4: 1492.0 H/S [T: 47c, RPM: 3535, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU5: 1484.0 H/S [T: 48c, RPM: 3373, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] Total: 8954.0 H/S
[2018-04-23 23:26:12] Pool sent a new job (ID: 264038743241690)
[2018-04-23 23:26:13] Pool accepted result 0x0000CEB1
[2018-04-23 23:26:16] Pool accepted result 0x000102BE
[2018-04-23 23:26:21] Pool accepted result 0x0000B950
[2018-04-23 23:26:24] Pool difficulty: 75939
[2018-04-23 23:25:53] Pool accepted result 0x000059B4
[2018-04-23 23:25:55] Pool accepted result 0x000044B1
[2018-04-23 23:25:55] Pool difficulty: 50625
[2018-04-23 23:25:55] Pool sent a new job (ID: 119620357058010)
[2018-04-23 23:25:58] Pool accepted result 0x0000EC14
[2018-04-23 23:26:03] Pool sent a new job (ID: 133028621855191)
[2018-04-23 23:26:11] GPU0: 1494.0 H/S [T: 51c, RPM: 3446, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU1: 1493.0 H/S [T: 51c, RPM: 3772, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU2: 1498.0 H/S [T: 48c, RPM: 3253, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU3: 1493.0 H/S [T: 47c, RPM: 3544, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU4: 1492.0 H/S [T: 47c, RPM: 3535, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] GPU5: 1484.0 H/S [T: 48c, RPM: 3373, CC: 1408 MHz, MC: 1100 MHz]
[2018-04-23 23:26:11] Total: 8954.0 H/S
[2018-04-23 23:26:12] Pool sent a new job (ID: 264038743241690)
[2018-04-23 23:26:13] Pool accepted result 0x0000CEB1
[2018-04-23 23:26:16] Pool accepted result 0x000102BE
[2018-04-23 23:26:21] Pool accepted result 0x0000B950
[2018-04-23 23:26:24] Pool difficulty: 75939
its not the miner your config/ clocking / volting settings sucks for 100%
Using OverDriveNTool:
[Profile_0]
Name=Vega64
GPU_P0=852;900;0
GPU_P1=991;900;0
GPU_P2=1084;900;0
GPU_P3=1138;900;0
GPU_P4=1150;900;0
GPU_P5=1202;900;0
GPU_P6=1212;905;0
GPU_P7=1408;925
Mem_P0=167;900;0
Mem_P1=500;900;0
Mem_P2=800;900;0
Mem_P3=1100;905
Fan_Min=3000
Fan_Max=4900
Fan_Target=65
Fan_Acoustic=1500
Power_Temp=70
Power_Target=-25
And PowerPlay:
_1100MHz_HBM_905mv
Wrong
Because using Cast XMR -->2055H/s
It looks like you are using default config.txt
Cast XMR automatically configures for you. For SRB, you need to change the intensity, worksize, and thread number until you find the ideal one.
thanks doktor for this miner (and I like the "iamagreedybastard" option, even if I don't use it!)
Mining heavy with 1xRX480 4 GB + 1xRX580 8 GB, the hashrate reported by the pool starts above 5000 H/S for the 2 cards when I launch the miner and decrease to 1600 H/S in something like 5 minutes... (Win 10, August blockchain driver, SRBMiner V1.4.1)
On the miner window, hashrate is always around 1600 H/S but I can clearly see that just after starting, it displays "pool accepted result xxxx" very fast corrsponding to higher hashrate and then the pace slowly decrease...
Any idea?
Mining heavy with 1xRX480 4 GB + 1xRX580 8 GB, the hashrate reported by the pool starts above 5000 H/S for the 2 cards when I launch the miner and decrease to 1600 H/S in something like 5 minutes... (Win 10, August blockchain driver, SRBMiner V1.4.1)
On the miner window, hashrate is always around 1600 H/S but I can clearly see that just after starting, it displays "pool accepted result xxxx" very fast corrsponding to higher hashrate and then the pace slowly decrease...
Any idea?
So about the dev pool mining. My 3 Vega rig never gets to submit any shares in the minute it is donating. Does it even help the devs when that happens?
I'm mining with heavy algo. Will dev donation work? If not, can I get a dev sumo or haven address to donate to using the charity feature?
charity mining was removed from version 1.2.4 , and this is exactly the reason why. Too much algos, there would be problems if you would mine for ex monerov7 but charity isn't the same algo..
Devfee works as expected, for every algo there should be no problems anymore.
Getting duplicate share errors when connecting to devfee.....
Re: Crex24.com - Cryptocurrency Exchange [Official Thread] (Fiat deposit/withdrawal)
I also had a great experience with Crex! I used a pool that said it would support mining to exchange. I found out later that the pool ignored the payment ID. I verified this by trying to mine to my own wallet with a payment ID and the payments came without payment ID.
I gave Crex the TIDs and my funds were soon credited. The problem wasn't on Crex's end but I was given a quick resolution. I will be doing as many of my trades there as I can
I gave Crex the TIDs and my funds were soon credited. The problem wasn't on Crex's end but I was given a quick resolution. I will be doing as many of my trades there as I can