Search content
Sort by
Showing 8 of 8 results by bitcoinsrule01
Re: [ANN][POOL][ZCL][KMD][0% fees] MiningTown: Zclassic & Komodo Mining Pool
Good news for the mining community. Mining Town has just dropped its pool fee from 1% to 0%. Can't beat that.
Now there is NO excuse not to join and profit together.
https://mining.town
Now there is NO excuse not to join and profit together.
https://mining.town
Re: [ANN][POOL][ZCL][KMD][0% fees] MiningTown: Zclassic & Komodo Mining Pool
If ZCL isn't your thing we have now added Komodo (KMD) as well. Come join us and check out the site. Compare the number of blocks we're mining with any ZCL calc. We are in fact solving more blocks and exceeding even the calcs claims of how many coins we should be mining in a day.
[ANN][POOL][ZCL][KMD][0% fees] MiningTown: Zclassic & Komodo Mining Pool
MiningTown - Join the community and profit together!
We are a small and growing pool of crypto loving miners. Our goal is to provide a rock solid and stable crypto mining pool that benefits all that join.
The pool has a 0% fee. What do you get for that small pool fee?
- US Based Servers (Pacific Northwest with low latency)
- Hefty DDOS Protection
- Pool infrastructure that will keep up with it's workload!
- Tested and tried with 50+ Blocks and counting solved and paid out.
- Startum ports for small and large miners or NiceHash.
- SSL mining support
- ZECProxy support https://github.com/BScrk/zecproxy
- US Based Servers (Pacific Northwest with low latency)
- Hefty DDOS Protection
- Pool infrastructure that will keep up with it's workload!
- Tested and tried with 50+ Blocks and counting solved and paid out.
- Startum ports for small and large miners or NiceHash.
- SSL mining support
- ZECProxy support https://github.com/BScrk/zecproxy
ZCL - Zclassic
Ports:
3073 Under 30K/sols
3074 SSL Under 30K/sols
3075 Over 30K/sols NiceHash
3076 SSL Over 30K/sols NiceHash
KMD - Komodo
Ports:
4073 Under 30K/sols
Ports:
3073 Under 30K/sols
3074 SSL Under 30K/sols
3075 Over 30K/sols NiceHash
3076 SSL Over 30K/sols NiceHash
KMD - Komodo
Ports:
4073 Under 30K/sols
Example for EWBF
miner --server zcl.mining.town --port 3073 --user your_address.name --pass x --intensity 64
Why try to start a pool now? Because competition is good. If your one of those miners that feel some of these pools today are a little toooo big we offer an alternative. Help us compete!
So come on down to MiningTown! It's a great time to be mining Zclassic. Come solve some blocks with us and see what you think.
This is slightly off topic, but I'm guessing you were able to login to SSH. Can anyone share the default root password for SSH?
I tried the one listed of 'miner1' but I'm not able to gain access. Version I just installed is v0019-1.
Thank you!
I tried the one listed of 'miner1' but I'm not able to gain access. Version I just installed is v0019-1.
Thank you!
Nothing is working for me...1.0.2.7, 1.0.2.9, or 1.0.3.1
the wallet will show that I am hashing but the pool show me doing nothing.
the wallet will show that I am hashing but the pool show me doing nothing.
same here..
Same. No hashrate on the pool and a 10X decrease in reported hashrate from the wallet.
Wouldn't hurt so bad that its not working if I didn't see a huge hashrate on the network. A few are benefiting that's for sure! It's working for some.
A few may be benefiting...but please remember the most that benefit are the orphans and their families that this project supports and reinforces. The developer is working HARD to get the issues under control.
It was expected because of the algorithm change.
Maybe in hindsight just a code change to automatically change block payout and the percentage of the payout to the cause of donations that this project supports.
While that may seem good...the purpose was to change the algorithm to make it stay resistant to GPU and ASIC...as far as I know.
This "hiccup" is only temporary. Like I said before....it will be stable again. I look forward to that. However sooner or later that may come.
This developer is the most active and understanding of our criticism that I have ever encountered!!!!!!!!
One thing I am not sure of...Are you the only one really running the day to day operations of all of this AWSEOME project?
First off I in no way meant any disrespect to the Admin or the the teams efforts to make this project a reality! I appreciate their hard work and dedication to this project and I wish it nothing but success. These children can use all the help they can get. I said what I did in an attempt to point out an unequal distribution in the network. It was not meant to be anything more or less.
Nothing is working for me...1.0.2.7, 1.0.2.9, or 1.0.3.1
the wallet will show that I am hashing but the pool show me doing nothing.
the wallet will show that I am hashing but the pool show me doing nothing.
same here..
Same. No hashrate on the pool and a 10X decrease in reported hashrate from the wallet.
Wouldn't hurt so bad that its not working if I didn't see a huge hashrate on the network. A few are benefiting that's for sure! It's working for some.
No, this is with all switches off, the only way to do it is to delete debug.log while client is running.
EDIT: When its deleted while running, it will stop writing log data.
EDIT: When its deleted while running, it will stop writing log data.
Is there a way to delete the debug.log on Windows when the file is being locked while the wallet is running?
Google "Windows unlocker". I don't know which program is free/best/easiest, but any one should do the trick.
Tried that but they all kill the process associated with the file. In this case the wallet itself. When you start up the wallet again it recreates the debug.log and starts filling it up again. Need to figure out a way to delete the file without killing the wallet process while deleting.
Regarding the hashrate: The problem is the big dogs have a RAID advantage because they have SSDs and multiple disks. The small guys have a single debug.log. We are spamming the log, and slowing the hashing down.
Any settings to disable writing data to debug.log?
EDIT: When its deleted while running, it will stop writing log data.
Is there a way to delete the debug.log on Windows when the file is being locked while the wallet is running?