List of known Webchain pools (WEB) :
https://miningpoolstats.stream/webchain
Live hashrate distribution, pool fees & minimum payment comparison.
Topic: 🔥🔥[ANN][MINTME]🌎MintMe.com Coin⚡️CPU mining⚡️DApps via Websites🚀No ICO/ASIC - page 33. (Read 84960 times)
April 08, 2019, 08:01:38 AM
April 08, 2019, 07:10:41 AM
Fork happened as planned, here is new wallet that you should use after the fork (old one will cause errors during transactions), https://github.com/webchain-network/webchain-wallet/releases/tag/v1.2.1
We also remind to update your miner that we released 2 weeks ago, https://github.com/webchain-network/webchain-miner/releases
We also remind to update your miner that we released 2 weeks ago, https://github.com/webchain-network/webchain-miner/releases
I've updated my miner on all my machines. I"m getting about 50% of the original hashrate. According to the network hashrate that appears to be widespread. Is this expected?
April 08, 2019, 07:06:18 AM
Fork happened as planned, here is new wallet that you should use after the fork (old one will cause errors during transactions), https://github.com/webchain-network/webchain-wallet/releases/tag/v1.2.1
We also remind to update your miner that we released 2 weeks ago, https://github.com/webchain-network/webchain-miner/releases
We also remind to update your miner that we released 2 weeks ago, https://github.com/webchain-network/webchain-miner/releases
April 06, 2019, 09:31:12 AM
Take a look at the progress of development here:
http://webchain.network/news/webchain-development-update-march-2019
Regards,
Pavel
It's nice to see that the project is developing no matter what. Web payments look very interesting. I will follow the updates. http://webchain.network/news/webchain-development-update-march-2019
Regards,
Pavel
April 03, 2019, 04:34:46 AM
Hi to all. Please read an update on our website regarding Coinroom http://webchain.network/news/coinroom-is-closing.
Regards,
Pavel
Regards,
Pavel
April 03, 2019, 03:44:04 AM
we remind you about upcoming fork on 8th April. If you just send and receive WEB, you will just have to download new wallet on 8th April after the fork (new wallet will show up only after fork happened). If you are miner - download new miner, it will automatically switch to new protocol if you are mining on a pool that was updated. If you are pool operator - please update, you have all new sources on our github. And if you have WEB on exchange, you don't have to do anything. CPUs should see hashrate jump after the fork.
March 29, 2019, 03:32:54 PM
Have you ever wanted to install own Webchain pool, but couldn't do it because didn't know certain details? It's not a problem anymore because we made a detailed guide about it. Check more here: https://webchain.network/news/detailed-guide-about-webchain-pool-installation
Regards,
Pavel
Regards,
Pavel
March 28, 2019, 08:14:40 PM
March 28, 2019, 12:05:10 PM
Take a look at the progress of development here:
http://webchain.network/news/webchain-development-update-march-2019
Regards,
Pavel
http://webchain.network/news/webchain-development-update-march-2019
Regards,
Pavel
March 27, 2019, 08:59:08 AM
Where can i find your roadmap?
Hi, in the whitepaper, page 6 https://webchain.network/Webchain_white_paper.pdf and almost at the bottom of the main page https://webchain.network/ .Regards,
Pavel
March 27, 2019, 07:46:12 AM
Krunzy.com Webchain (WEB) Mining Pool 
Pool: Krunzy Webchain Pool
Website: http://webchain.pool.krunzy.com
Location: USA
Pool Fee: 0.4%
Min Payout: 1 WEB every 60 minutes
Features:
1000-100000 VariDiff webchain.mine.krunzy.com:1111
10000-100000 VariDiff webchain.mine.krunzy.com:2222
25000 StaticDiff webchain.mine.krunzy.com:3333
75000 StaticDiff webchain.mine.krunzy.com:4444
150000 StaticDiff webchain.mine.krunzy.com:5555
Getting Started/ Miner Software: http://webchain.pool.krunzy.com/#/help
More here: http://krunzy.com/webchain-mining-pool/
Good luck!
http://krunzy.com
Pool: Krunzy Webchain Pool
Website: http://webchain.pool.krunzy.com
Location: USA
Pool Fee: 0.4%
Min Payout: 1 WEB every 60 minutes
Features:
- Individual worker statistics
- Pool Blocks History with luck and linked blockchain explorer
- Payment History
1000-100000 VariDiff webchain.mine.krunzy.com:1111
10000-100000 VariDiff webchain.mine.krunzy.com:2222
25000 StaticDiff webchain.mine.krunzy.com:3333
75000 StaticDiff webchain.mine.krunzy.com:4444
150000 StaticDiff webchain.mine.krunzy.com:5555
Getting Started/ Miner Software: http://webchain.pool.krunzy.com/#/help
More here: http://krunzy.com/webchain-mining-pool/
Good luck!
http://krunzy.com
March 27, 2019, 07:32:51 AM
Where can i find your roadmap?
March 26, 2019, 03:52:20 PM
I see price is going up and buy orders as well for webchain 
It was expected: Buy the news before the release and sell after the release. Easy money:we have released new wallet, although give it few days to mature if you are cautious 
We tested it but we could have missed something. https://github.com/webchain-network/webchain-wallet/releases. It should improve performance on busy wallets + many random errors. Also introduces webchain:// addresses in browser. full changelog on github
We tested it but we could have missed something. https://github.com/webchain-network/webchain-wallet/releases. It should improve performance on busy wallets + many random errors. Also introduces webchain:// addresses in browser. full changelog on github March 26, 2019, 03:49:53 PM
we have released new wallet, although give it few days to mature if you are cautious We tested it but we could have missed something. https://github.com/webchain-network/webchain-wallet/releases. It should improve performance on busy wallets + many random errors. Also introduces webchain:// addresses in browser. full changelog on github
We tested it but we could have missed something. https://github.com/webchain-network/webchain-wallet/releases. It should improve performance on busy wallets + many random errors. Also introduces webchain:// addresses in browser. full changelog on github March 23, 2019, 06:54:40 PM
Anyone willing to share their hash-rate?
I'm currently getting around 500 h/s on a 2950x. Can't seem to push it any higher than that using the cryptonight-webchain miner. Is that a good speed?
{
"algo": "cryptonight-webchain",
"av": 0, // algorithm variation, 0 auto select
"background": false, // true to run the miner in the background
"colors": true, // false to disable colored output
"cpu-affinity": null, // set process affinity to CPU core(s), mask "0x3" for cores 0 and 1
"cpu-priority": null, // set process priority (0 idle, 2 normal to 5 highest)
"donate-level": 5, // donate level, mininum 1%
"huge-pages": true,
"hw-aes": null,
"log-file": null, // log all output to a file, example: "c:/some/path/webchain-miner.log"
"max-cpu-usage": 75, // maximum CPU usage for automatic mode, usually limiting factor is CPU cache not this option.
"print-time": 60, // print hashrate report every N seconds
"retries": 5, // number of times to retry before switch to backup server
"retry-pause": 5, // time to pause between retries
"safe": false, // true to safe adjust threads and av settings for current CPU
"threads": 16, // number of miner threads
"user-agent": null,
"watch": false,
I'm currently getting around 500 h/s on a 2950x. Can't seem to push it any higher than that using the cryptonight-webchain miner. Is that a good speed?
{
"algo": "cryptonight-webchain",
"av": 0, // algorithm variation, 0 auto select
"background": false, // true to run the miner in the background
"colors": true, // false to disable colored output
"cpu-affinity": null, // set process affinity to CPU core(s), mask "0x3" for cores 0 and 1
"cpu-priority": null, // set process priority (0 idle, 2 normal to 5 highest)
"donate-level": 5, // donate level, mininum 1%
"huge-pages": true,
"hw-aes": null,
"log-file": null, // log all output to a file, example: "c:/some/path/webchain-miner.log"
"max-cpu-usage": 75, // maximum CPU usage for automatic mode, usually limiting factor is CPU cache not this option.
"print-time": 60, // print hashrate report every N seconds
"retries": 5, // number of times to retry before switch to backup server
"retry-pause": 5, // time to pause between retries
"safe": false, // true to safe adjust threads and av settings for current CPU
"threads": 16, // number of miner threads
"user-agent": null,
"watch": false,
I think you should be getting double that.
Here are some tips:
1. If you're using Windows, make sure you're running the miner as admin, otherwise it will not allow for huge pages.
2. Setting cpu affinity helps. Instead of "threads": 16, use this to affine the threads each to a physical core:
"threads": [
{"low_power_mode": false, "affine_to_cpu": 0 },
{"low_power_mode": false, "affine_to_cpu": 2 },
{"low_power_mode": false, "affine_to_cpu": 4 },
etc. until 16 threads...
{"low_power_mode": false, "affine_to_cpu": 30 }
],
I've spent several hours trying to figure out why I can't get a better hashrate. I seem to be getting the best hashrate when using 8 threads (which maxes out around 700). After doing a TON of googling and reading through forums I realized that my solution was much simpler... I have 8 slots on my motherboard from RAM. I placed my ram sticks on one side of the motherboard (which means that the CPU couldn't use all 16 cores to their full potential) I moved one stick over to the other side and I can get a max of 1400 h/s on 16 threads. Although, i've got this tuned to 12 cores to try and keep the temp down. (I'm still getting 1050 h/s which seems reasonable enough)
If you want to keep your temp and power consumption down, consider running 8 dual threads instead of 16 normal. Just change low_power_mode": false to low_power_mode": true in all (now 8 ) threads. You'll be running half the number of threads, but al of them will use double cache. You should be getting around 1100 H instead of 1400, but with 25% CPU usage instead of 50%.
March 23, 2019, 04:29:44 PM
I see price is going up and buy orders as well for webchain
March 23, 2019, 04:29:03 PM
Nice, what a cool looking motherboard. I guess that is specific for your 2950x. Never seen such a thing and i build mining and gaming rigs for the last 10 years lol. But never really looked deep into that CPU and board. Impressive!! thanks for sharing.
March 23, 2019, 08:04:52 AM
Thats an awesome hash rate now
Not sure if what your referring to is this, but ram slots determine whether or not you will see true DDR from it. I just fixed my sons gaming rig, and his step brother had moved the ram around on it and had lost its Dual MODE DDR. Once the ram sticks were configured back, the motherboard bios stated ram was in DDR Dual Mode (and not single) anymore. It wasn't before. And his gaming has improved now. ok, was just wondering if that had maybe the impact on your CPU? lol... but glad to hear you got it straight. Thats fast!!
PS: I am getting 363 hashes on AMD 8350 8 core
Not sure if what your referring to is this, but ram slots determine whether or not you will see true DDR from it. I just fixed my sons gaming rig, and his step brother had moved the ram around on it and had lost its Dual MODE DDR. Once the ram sticks were configured back, the motherboard bios stated ram was in DDR Dual Mode (and not single) anymore. It wasn't before. And his gaming has improved now. ok, was just wondering if that had maybe the impact on your CPU? lol... but glad to hear you got it straight. Thats fast!!
PS: I am getting 363 hashes on AMD 8350 8 core
My motherboard is very similar to this one:
https://c1.neweggimages.com/NeweggImage/ProductImage/13-157-784-V06.jpg
I've seen on dual CPU motherboards that each section of 4 ram slots is dedicated to 1 CPU. If you put 2 CPUs in and only use 1 section of ram slots then only 1 CPU will actually work. (Not sure if that is universal for all motherboards). I placed all of my ram onto the right side of the motherboard & could max out my hashing on 8/16 cores. So my assumption is that my OS can see all 16 cores in the CPU, but can only utilize 8 to their full potential. Moving a ram stick from the right side onto the left instantly fixed my problem and let me use up to 16/16 cores.
March 22, 2019, 09:07:28 PM
Thats an awesome hash rate now
Not sure if what your referring to is this, but ram slots determine whether or not you will see true DDR from it. I just fixed my sons gaming rig, and his step brother had moved the ram around on it and had lost its Dual MODE DDR. Once the ram sticks were configured back, the motherboard bios stated ram was in DDR Dual Mode (and not single) anymore. It wasn't before. And his gaming has improved now. ok, was just wondering if that had maybe the impact on your CPU? lol... but glad to hear you got it straight. Thats fast!!
PS: I am getting 363 hashes on AMD 8350 8 core
Not sure if what your referring to is this, but ram slots determine whether or not you will see true DDR from it. I just fixed my sons gaming rig, and his step brother had moved the ram around on it and had lost its Dual MODE DDR. Once the ram sticks were configured back, the motherboard bios stated ram was in DDR Dual Mode (and not single) anymore. It wasn't before. And his gaming has improved now. ok, was just wondering if that had maybe the impact on your CPU? lol... but glad to hear you got it straight. Thats fast!!
PS: I am getting 363 hashes on AMD 8350 8 core
March 22, 2019, 07:13:52 AM
Anyone willing to share their hash-rate?
I'm currently getting around 500 h/s on a 2950x. Can't seem to push it any higher than that using the cryptonight-webchain miner. Is that a good speed?
{
"algo": "cryptonight-webchain",
"av": 0, // algorithm variation, 0 auto select
"background": false, // true to run the miner in the background
"colors": true, // false to disable colored output
"cpu-affinity": null, // set process affinity to CPU core(s), mask "0x3" for cores 0 and 1
"cpu-priority": null, // set process priority (0 idle, 2 normal to 5 highest)
"donate-level": 5, // donate level, mininum 1%
"huge-pages": true,
"hw-aes": null,
"log-file": null, // log all output to a file, example: "c:/some/path/webchain-miner.log"
"max-cpu-usage": 75, // maximum CPU usage for automatic mode, usually limiting factor is CPU cache not this option.
"print-time": 60, // print hashrate report every N seconds
"retries": 5, // number of times to retry before switch to backup server
"retry-pause": 5, // time to pause between retries
"safe": false, // true to safe adjust threads and av settings for current CPU
"threads": 16, // number of miner threads
"user-agent": null,
"watch": false,
I'm currently getting around 500 h/s on a 2950x. Can't seem to push it any higher than that using the cryptonight-webchain miner. Is that a good speed?
{
"algo": "cryptonight-webchain",
"av": 0, // algorithm variation, 0 auto select
"background": false, // true to run the miner in the background
"colors": true, // false to disable colored output
"cpu-affinity": null, // set process affinity to CPU core(s), mask "0x3" for cores 0 and 1
"cpu-priority": null, // set process priority (0 idle, 2 normal to 5 highest)
"donate-level": 5, // donate level, mininum 1%
"huge-pages": true,
"hw-aes": null,
"log-file": null, // log all output to a file, example: "c:/some/path/webchain-miner.log"
"max-cpu-usage": 75, // maximum CPU usage for automatic mode, usually limiting factor is CPU cache not this option.
"print-time": 60, // print hashrate report every N seconds
"retries": 5, // number of times to retry before switch to backup server
"retry-pause": 5, // time to pause between retries
"safe": false, // true to safe adjust threads and av settings for current CPU
"threads": 16, // number of miner threads
"user-agent": null,
"watch": false,
I think you should be getting double that.
Here are some tips:
1. If you're using Windows, make sure you're running the miner as admin, otherwise it will not allow for huge pages.
2. Setting cpu affinity helps. Instead of "threads": 16, use this to affine the threads each to a physical core:
"threads": [
{"low_power_mode": false, "affine_to_cpu": 0 },
{"low_power_mode": false, "affine_to_cpu": 2 },
{"low_power_mode": false, "affine_to_cpu": 4 },
etc. until 16 threads...
{"low_power_mode": false, "affine_to_cpu": 30 }
],
I've spent several hours trying to figure out why I can't get a better hashrate. I seem to be getting the best hashrate when using 8 threads (which maxes out around 700). After doing a TON of googling and reading through forums I realized that my solution was much simpler... I have 8 slots on my motherboard from RAM. I placed my ram sticks on one side of the motherboard (which means that the CPU couldn't use all 16 cores to their full potential) I moved one stick over to the other side and I can get a max of 1400 h/s on 16 threads. Although, i've got this tuned to 12 cores to try and keep the temp down. (I'm still getting 1050 h/s which seems reasonable enough)
Jump to: