🔥🔥[ANN][MINTME]🌎MintMe.com Coin⚡️CPU mining⚡️DApps via Websites🚀No ICO/ASIC - page 47.

whotheff

member

Activity: 762

Merit: 35

Quote from: albertod on August 07, 2018, 08:53:48 AM

Quote from: whotheff on August 05, 2018, 01:30:06 PM

Hi Team, are you planning to switch to GPU mining?

No, we aren't. It's against the main goals of the project. Keep in mind that Webchain Network was designed to allow CPU users to enjoy the profitability of a cryptocurrency where GPU mining is not more profitable than CPU mining and where ASICs are not allowed. I invite you to have a look at our whitepaper.

I've been CPU mining since the very begining. My hashrate is modest, only 140h/s.
----------------------
See the above posts for working GPU miners, now see the Network hashrate bump from 2 Kh/s to 1.5 Mh/s.
Now tell me again, is this coin a a real CPU only coin, or CPU miners are fools?

Are you planning to:

1. Fork to disable GPU mining,
2. or keep your eyes closed
3. or become a CPU+GPU minable coin?

sundownz06

newbie

Activity: 110

Merit: 0

Quote from: monkins1010 on August 18, 2018, 03:02:54 PM

also updated nvidia miner to give worker id

https://github.com/monkins1010/LOUD-Webchain-miner-nvidia/releases/tag/v1.1

ive bodged it a bit and used the password as the user id .. but it works..

That did the trick =)

Tangri

newbie

Activity: 48

Merit: 0

So far so good. 3% duplicate shares/compute error but reasonable. Finally I have pointed my rigs to LOUD.

Lets see if they all stay alive for few days.

Now, how about that 100k difficulty port, say 6666. ??

Thanks bro.

monkins1010

jr. member

Activity: 41

Merit: 1

AMD updated works on multi GPUS

https://github.com/monkins1010/LOUD-Mining-Webchain-AMD/releases/tag/v1.38

put "worker-id" : "Whateva" in the pools section of the json to add a rig name.

also updated nvidia miner to give worker id

https://github.com/monkins1010/LOUD-Webchain-miner-nvidia/releases/tag/v1.1

ive bodged it a bit and used the password as the user id .. but it works..

sundownz06

newbie

Activity: 110

Merit: 0

Quote from: Tangri on August 18, 2018, 12:12:05 AM

Quote from: sundownz06 on August 17, 2018, 06:59:46 AM

Quote from: Tangri on August 16, 2018, 05:58:30 PM

Quote from: monkins1010 on August 16, 2018, 04:25:04 PM

https://github.com/monkins1010/LOUD-Mining-Webchain-AMD/releases/tag/v1

updated please test

Thanks for the new miner. still have 2 main problems.

1. rig id isn't reflected at pool. Still shows up as worker id "0", no matter what you put into config.json.

I have this issue on the nVidia miner as well.

This is too bad for monkins as it fails on dev donation. I would point my cpus and gpus to loudmining but I can't at this point due to conflict of duplicated shares. All my cpus and gpus are pointed to other pools now. Or if anyone found good solution, kindly share please.

I am using the nVidia miner on one test machine -- it seems to submit shares fine for the most part. Just doesn't show worker ID.

I have not tried the AMD miner just yet.

sshiddiq67

newbie

Activity: 98

Merit: 0

The Webchain is a transparent, egalitarian blockchain protocol that holds US and smart contracts, is mined with a Webchain, users can use Internet of Things resources or any device that can create JavaScript.

Tangri

newbie

Activity: 48

Merit: 0

Quote from: sundownz06 on August 17, 2018, 06:59:46 AM

Quote from: Tangri on August 16, 2018, 05:58:30 PM

Quote from: monkins1010 on August 16, 2018, 04:25:04 PM

https://github.com/monkins1010/LOUD-Mining-Webchain-AMD/releases/tag/v1

updated please test

Thanks for the new miner. still have 2 main problems.

1. rig id isn't reflected at pool. Still shows up as worker id "0", no matter what you put into config.json.

I have this issue on the nVidia miner as well.

This is too bad for monkins as it fails on dev donation. I would point my cpus and gpus to loudmining but I can't at this point due to conflict of duplicated shares. All my cpus and gpus are pointed to other pools now. Or if anyone found good solution, kindly share please.

Tangri

newbie

Activity: 48

Merit: 0

Quote from: Kinsey on August 17, 2018, 03:47:20 PM

Quote from: Tangri on August 16, 2018, 05:58:30 PM

Quote from: monkins1010 on August 16, 2018, 04:25:04 PM

https://github.com/monkins1010/LOUD-Mining-Webchain-AMD/releases/tag/v1

updated please test

2. Single gpu works ok. But soon as you mutithread it on single gpu or single thread on multiple gpus, it will spit out "duplicate shares" everytime share is found. and banned. Perhaps, internal checker for duplicates isn't working as intended. Even on single threaded gpu, it will spit out duplicates share if difficulty is low enough. i.e. when dev donate mode starts, half the shares are rejected/briefly banned because it connects to low difficulty port.

I ran into this problem. Maybe this can be fixed if I change some parameters in the configuration file?

Well let me know if you make it work.

Network hash is now near 2MH where is was 300KH just about a week ago. Someone got a good working GPU miner farm or botnet attached. So much for CPU/Web secured network.

Kinsey

member

Activity: 404

Merit: 10

Quote from: Tangri on August 16, 2018, 05:58:30 PM

Quote from: monkins1010 on August 16, 2018, 04:25:04 PM

https://github.com/monkins1010/LOUD-Mining-Webchain-AMD/releases/tag/v1

updated please test

2. Single gpu works ok. But soon as you mutithread it on single gpu or single thread on multiple gpus, it will spit out "duplicate shares" everytime share is found. and banned. Perhaps, internal checker for duplicates isn't working as intended. Even on single threaded gpu, it will spit out duplicates share if difficulty is low enough. i.e. when dev donate mode starts, half the shares are rejected/briefly banned because it connects to low difficulty port.

I ran into this problem. Maybe this can be fixed if I change some parameters in the configuration file?

vitmak

newbie

Activity: 24

Merit: 0

Quote from: monkins1010 on August 16, 2018, 04:25:04 PM

https://github.com/monkins1010/LOUD-Mining-Webchain-AMD/releases/tag/v1

updated please test

Hi monkins1010. I have two Radeon RX560 computers. When I start loud-amd error - " THREAD #0 COMPUTE ERROR ".
Windows 10 64 bit.

sundownz06

newbie

Activity: 110

Merit: 0

Quote from: Tangri on August 16, 2018, 05:58:30 PM

Quote from: monkins1010 on August 16, 2018, 04:25:04 PM

https://github.com/monkins1010/LOUD-Mining-Webchain-AMD/releases/tag/v1

updated please test

Thanks for the new miner. still have 2 main problems.

1. rig id isn't reflected at pool. Still shows up as worker id "0", no matter what you put into config.json.

I have this issue on the nVidia miner as well.

niko2004x

member

Activity: 126

Merit: 10

Quote from: monkins1010 on August 16, 2018, 04:25:04 PM

https://github.com/monkins1010/LOUD-Mining-Webchain-AMD/releases/tag/v1

updated please test

Source and released version does not match?

Tangri

newbie

Activity: 48

Merit: 0

Quote from: monkins1010 on August 16, 2018, 04:25:04 PM

https://github.com/monkins1010/LOUD-Mining-Webchain-AMD/releases/tag/v1

updated please test

Thanks for the new miner. still have 2 main problems.

1. rig id isn't reflected at pool. Still shows up as worker id "0", no matter what you put into config.json.

2. Single gpu works ok. But soon as you mutithread it on single gpu or single thread on multiple gpus, it will spit out "duplicate shares" everytime share is found. and banned. Perhaps, internal checker for duplicates isn't working as intended. Even on single threaded gpu, it will spit out duplicates share if difficulty is low enough. i.e. when dev donate mode starts, half the shares are rejected/briefly banned because it connects to low difficulty port.

I find myself rig id is major problem for me to use my gpus at loudmining.

For your info, my AMD frontier editions gets 700ish hash at stock 1536/8 setting.

Edit: incident of really high duplicate shares found during the dev donation is because I had 2 miner, one for each gpu, pointed at 2 different pool. So when dev donation started, since both miner has default rig id of 0, and from same IP address, they were colliding with each other, resulting in duplicate shares. Other than that, am still experiencing duplicate shares with 2 or more thread from same miner, and occasional duplicates out of no where.

monkins1010

jr. member

Activity: 41

Merit: 1

https://github.com/monkins1010/LOUD-Mining-Webchain-AMD/releases/tag/v1.38

updated please test got miners for all platforms now

Andzhig

jr. member

Activity: 184

Merit: 3

Quote from: MusicByKang on August 16, 2018, 01:34:53 AM

I use Google Translator.

Nothing can be done about it. For the interest remove 1 sign from the end of the address webcoin (it seems that the addresses for 1 character difference in length) and look in the webchain explorer can there that flew there https://explorer.webchain.network/home but even if it has arrived, access to coins on it does not get.

MusicByKang

newbie

Activity: 2

Merit: 0

I use Google Translator.

Help me
I made a mistake.
I sent it to the exchange's webcoin (web) address.
yes webcoin (web) ....
I was stupid to see the web

I have successfully passed status to my wallet.
Obviously webcoin (web) addresses do not come in

How can I find my webchain coin
The number sent was 3,000 coins
Wait for an answer

sundownz06

newbie

Activity: 110

Merit: 0

Quote from: albertod on August 15, 2018, 09:19:13 AM

Quote from: sundownz06 on August 14, 2018, 03:16:38 PM

I cannot get the Worker ID to show up on the official pool at all... anyone know where I went wrong?

Hello! You don't have to modify "worker-id" in the API array, only in the pool array. and no need to set a password on the json file. But I see those are not the configs of the CPU miner officially released by the team, you can join Webchain discord server and contact the developers who created that version you're using.

Thanks -- luckily the owner of the Loudmining pool helped me in Discord =) Got it running!

I am using the official miner but under Linux... didn't seem to have a config.json so I used the standard XMRIG as a template and changed my values.

albertod

newbie

Activity: 196

Merit: 0

Quote from: sundownz06 on August 14, 2018, 03:16:38 PM

I cannot get the Worker ID to show up on the official pool at all... anyone know where I went wrong?

Hello! You don't have to modify "worker-id" in the API array, only in the pool array. and no need to set a password on the json file. But I see those are not the configs of the CPU miner officially released by the team, you can join Webchain discord server and contact the developers who created that version you're using.

siegep

jr. member

Activity: 183

Merit: 1

Quote from: wafdawg on August 10, 2018, 01:45:04 AM

WEB should also have a large hidden Mind Pool. The Hash of Loud Mind Pool is not high.

What pool you are talking about ?

justincase1911

newbie

Activity: 17

Merit: 0

Quote from: albertod on August 15, 2018, 08:23:52 AM

Webchain was added to CoinIMP, it's been tested and it's fully working.

People are already withdrawing WEB from their CoinIMP wallets.
We set payout to 100% so every mined WEB goes to your wallet (minus orphan blocks rate, since webchain has it higher than monero).
Webchain withdraw threshold is much lower that the threshold for Monero.
No marketing actions have been done yet with our users because we are still working on changing the main page to have coinimp.com look like an advertisement site for WEB.
The marketing campaign to inform our that WEB can be mined via CoinIMP should be started later this month.
The team keeps working on other projects related to WEB that should be revealed soon.

Visit https://www.coinimp.com/ for more information. Remember, most of our community is available on our discord server.

i like the dashboard of coinimp with monero and web already listed. thumbs up.
no offense but maybe downsize the font and the blue lable on the dashboard a little bit like 70%.

great work and nice project keep going on guys we are already getting attention

Topic: 🔥🔥[ANN][MINTME]🌎MintMe.com Coin⚡️CPU mining⚡️DApps via Websites🚀No ICO/ASIC - page 47. (Read 85211 times)