Topic: [ANN][Groestl/MyriadGroestl] Pool closed - page 9. (Read 37023 times)

See example.conf that is included in the installer zip file. It is for r9 270x and/or r9 290

Some cards cannot go as low as 150.
Try to find your minimum value. It could be 900 or 1150. You'll have to experiment

Normal hashing parameter was introduced exactly for this reason. To be able to switch between grs and dmd pools in realtime.

See example.conf. You also should be able to specify normal-hashing true, false in command line if you are specifying two pools: dmd and grs

And these are my payouts for 28 June:

Tell me how much I owe you and please move on to some other pool.

I feel that this thread is overloaded with your complaints.

> Are you afraid of making this public? I've sent you 2 PMs, one of which was unrelated but to this date answers to none. So I will keep posting here.

Of course not. After all, this is a self moderated thread and I can just delete your messages if I feel like it. :-)
But as I said, I am not checking this thread daily. And if somebody needs my attention urgently (like if payouts are not working or stratum is offline) - just PM me.

I chose to ignore this PM of yours:

and have replied to all your other PM questions.
Which there were a few :-)

>Good but that doesn't dispense you from answering comments here specially when you are running a pool and people are paying a fee.

Agreed, but I am still not going to read this thread regularly.
And if something is broken - just PM me.



> Not sure where the problem is coming from, but I am mining in your pool, so naturally I come to you first. The network has been running ok apart from the assertion problem and the PoS on June 26. Since that, the network has been up and running. Consult with DMD team before making such statements.

Why should I consult? I saw that there is a problem with DMD network.
I had the same problem when I was forking Groestlcoin.

> As for the 2.0.2.2 wallet.... Well, I don't mean to be brutal here, but I was the VERY FIRST one to test it following the updated code by Danbi so I am pretty much aware of the update. Your pool went down for ~ an hour or so (on June 30 @ ~7.18am Bangkok time) when you tried to update the wallet (which is to be expected) and complained about the assertion problem which had been disscussed profusely all 4 days prior your pool's wallet update.

That's true. But all pools go down for some time. Even danbi's.
I had the assert after updating to the new wallet and then had to find and redownload the blockchain.
To return to your question about DMD devs, I feel like they should devote a bit more time to testing.


> Please don't deflect. First, let's talk about the the problem and the ~20 coins I am not seing. I am simply investigating the reasons.

Basically, I think that you are not missing any coins.
I was mining DMD myself on exactly this pool and did not get any other complaints.

As I said before, I'm running NOMP pool software and it pays out all the matured blocks completely without leaving anything in the running DMD wallet.


> I reiterate, there are no "more" or "less", there is simply NOTHING for 6 straight hours in a row.
> As for the graph, that one is from today. I was refering to June 28 and July 1st. Thank you for checking your logs. Appreciated.

Unfortunately, it is not possible to rewind the graph to those dates. But please look at it next time you have problems.

As for these 6 missing hours, perhaps you had no internet connection or forgot about it and actually was mining some other coin or something similar to this.


Please don't get me wrong, I don't have anything against you personally.

It's just that replying to your messages and trying to explain myself is taking too much of my time and decreases my motivation to proceed with any improvements.

Also, I think it doesn't work in my favour and people who read this think that it is a scam or something like that and avoid.

I feel like you are not happy with the pool and non-transparency so I recommend that you return to danbi's pool.
If you think that I owe you 20 DMD or some other amount - let me know and I'll pay you.

I am still waiting for your answer.

"optimized" kernel will get myriad-groestl support shortly (you can already see me testing it on port 60002).

So it'll be possible to mine myriadcoin and saffroncoin (also futurecoin, but I think it is already dead).

R9 290 gives about 33.5 MH/s. Perhaps I'll be able to make it faster.

I'll keep you posted.

PS: Getting past 20 MH/s on Groestl appeared to be quite hard. I still am hoping that I can achieve at least 22MH/s on R9 290 using the current algorithm, but it'll probably be some time later.

community, please confirm or disprove this point:
on a pool of cryptohunger.com:81 first of payment occur in 3 hours, but on my supervision if to stop mining, that payments occur only in the last hour, and not as it should be the last 3 hours. is this true? I noticed it already 2 times.
basically I get every hour from 9 to 25 ATH depending on the difficulty, but if stop mining, that comes only 4+ ATH and all this for the last 3 hours.

why am nit getting any accepts? nor rejects my miners says setting GPUs for idle???

Hi,

Why are we three on this pool for grs ? :p

See ya

Are you afraid of making this public? I've sent you 2 PMs, one of which was unrelated but to this date answers to none. So I will keep posting here.


Good but that doesn't dispense you from answering comments here specially when you are running a pool and people are paying a fee.


Not sure where the problem is coming from, but I am mining in your pool, so naturally I come to you first. The network has been running ok apart from the assertion problem and the PoS on June 26. Since that, the network has been up and running. Consult with DMD team before making such statements.

As for the 2.0.2.2 wallet.... Well, I don't mean to be brutal here, but I was the VERY FIRST one to test it following the updated code by Danbi so I am pretty much aware of the update. Your pool went down for ~ an hour or so (on June 30 @ ~7.18am Bangkok time) when you tried to update the wallet (which is to be expected) and complained about the assertion problem which had been disscussed profusely all 4 days prior your pool's wallet update.


Payments are supposed to be done according to the hash power hourly. Yes solving blocks is luck based. So are you saying that we had no luck for over 6 hours? There was twice, no payment for ~6 hours in a row... I am not sure if this is luck related but if it is then everyone mining DMD in your pool should nornally have the exact same thing happen to them. If anyone reads this and mines at DMD at cryptohunger, could you please check you transaction on June 28 and July 1st?


Please don't deflect. First, let's talk about the the problem and the ~20 coins I am not seing. I am simply investigating the reasons.


I reiterate, there are no "more" or "less", there is simply NOTHING for 6 straight hours in a row.

As for the graph, that one is from today. I was refering to June 28 and July 1st. Thank you for checking your logs. Appreciated.

If you need me - please PM.

I'm not reading this thread regularly and devoting all time to making a new OpenCL kernel.

I'm not aware of any problems and am mining DMD myself with 90 MH/s.

Possibly it is related to some troubles with the Diamondcoin network (BTW pool is using the latest 2.0.2.2 wallet).
The pool performs payouts based on the number of coins earned per hour. This is purely luck based.

If you feel the this pool is not transparent enough or is stealing your coins, please move to some other pool.
This is your decision.

You can see statistics here visually:
(Sometimes there is more and sometimes there is less "light blue")

Glad I decided to read up on the thread a bit before moving over to his pool. I am ok with a fee and all but transparency while mining is a must.

Srcxx where are you.....?

Why did I not receive any payment today between 6am and 12pm? Payments are supposed to happen every hour and my miner was very well running. The loss is estimated at ~10DMD

Same happened on June 28. Between 5am and 12pm. The loss is estimated at ~10DMD

The total estimated loss = ~20 DMD

Stratum is down.

1 - What does "doesn't work" mean? Please be precise and provide an error code or anything that can be used to debug your problem.
2 - For 270x use groestlcoinPitcairn256l4.bop or groestlcoinTahiti256l4.bop
3 - As adviced by OP 14.6 Beta are the drivers to be used. Whethere or not it is a requirement to function that I can't tell. But others with 270x have been able to use the optimized kernel with their 270x cards.
4 - Noted.
5 - Read: https://bitcointalksearch.org/topic/m.7411804
6 - Try using the .bop file from version 1.2.4. For some reason the .bop file of 1.2.5 gives me an error on my 280x cards. Not the same error though.

Finally have you tried using the normal kernel instead of the optimized one?

Optional but recommended: use your own address and try with only one pool to start with...

1- tried that..didnt work
2- kernel corresponding to the card? i am trying to use "optimized" kernel for diamondcoin
3- currently using 13.12 and dont wanna change unless absolutely necessary
4- will do ...curently on remote
5- using the example.cfg as you suggested (minus oc settings)...didnt even change the payment address.