Bitcoin Forum
July 21, 2019, 12:09:11 PM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 15 16 17 »  All
  Print  
Author Topic: [ANN][Groestl/MyriadGroestl] Pool closed  (Read 36624 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
paladin281978
Hero Member
*****
Offline Offline

Activity: 742
Merit: 500



View Profile
June 27, 2014, 04:16:26 AM
 #121


the pool is not transparent statistics, so people are not happy ...
only srcxxx is to blame that chose this template for a pool with no clear statistics, not people.
but I think the statistics correct. but not transparent Smiley

1563710951
Hero Member
*
Offline Offline

Posts: 1563710951

View Profile Personal Message (Offline)

Ignore
1563710951
Reply with quote  #2

1563710951
Report to moderator
1563710951
Hero Member
*
Offline Offline

Posts: 1563710951

View Profile Personal Message (Offline)

Ignore
1563710951
Reply with quote  #2

1563710951
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1563710951
Hero Member
*
Offline Offline

Posts: 1563710951

View Profile Personal Message (Offline)

Ignore
1563710951
Reply with quote  #2

1563710951
Report to moderator
polanskiman
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
June 27, 2014, 05:04:55 AM
 #122


the pool is not transparent statistics, so people are not happy ...
only srcxxx is to blame that chose this template for a pool with no clear statistics, not people.
but I think the statistics correct. but not transparent Smiley


Yes I agree the website needs some more detailed stats and also needs to be a bit more polished. The Getting Started and API pages are also not complete.

Not sure why you are talking about blame though. That's a choice scrxxx did to select NOMP over MPOS and there is nothing wrong with that. Now, some people might like it some others might not, but then it become their choice to mine elsewhere. Smiley

What I see though is that most people tend to complaint quite quick whitout trying to figure out why things are the way they are. I have noticed in general that people don't simply read past posts or OP properly. Impatience. I also remember being like that myself.

Anyways, yes the pool needs to be polished and I beleive it's a priority.

BTC: 1JnH2HVoWnDubGmrXintsNWEaByGRjY8wL
DMD: dZuojpnwkmzqUegQaFk7ynDY8p7zAmG25H
XCN: CKnXnjXsVJzXgqEEqjsMRRc7ohkk6jHsb6
srcxxx
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250


View Profile WWW
June 27, 2014, 07:53:52 AM
 #123

Hi Guys!

First of all, thanks for your feedback. Both positive and negative.

Regarding the pool and the lack of statistics...
As I already said, I would like to have statistics myself. Pools like http://max.1gh.com/ and http://dwarfpool.com/tac have nice statistics and stuff.
But they are using some custom pool code and it is not open source. I.e. I don't have access to it.

MPOS is open source and I even have it running on grs.cryptohunger.com. But... I hate it.
Had too many troubles with it (BTW, I had to write my own stratum implementation for Groestlcoin which took 2 weeks).
So I am not going to use MPOS.

When you are just starting mining or switching to a new coin, you want statistics. I get that. But once you played with it for a few days, you just leave your rigs hashing and find something else to occupy your time. Just look at the 1.13 GH whale mining Dokdocoin (BTW, thanks for staying on my pool, whoever you are). I'm sure he is very sensitive to the amount of coins he gets every hour.

NOMP is a new project. It is growing fast. It is very good conceptually (very low server load, no risk for pool operator as all coins are completely paid out). Just about a month ago it didn't have worker statistics. Now it is added: http://cryptohunger.com:81/workers
There is a feature request for statistics in NOMP and I'm hoping it'll be added shortly.

I encourage you to give it a try with the "optimized" kernel. Leave it running say overnight.
In the morning check transactions in your wallet. There will be some coins sent to you every hour. That's your statistics.
If you are happy with it - please keep mining.
If you are not - no problem also. Use some other pool with "groestlcoin" kernel.
Yes, the non-optimized kernel is slower. But it is still faster than the sph-sgminer.

I am planning to continue working on grs-sgminer until there is stuff to optimize (currently I see 5 potential changes that might improve hashrate, that is without completely changing the algo, like ccMiner KillerGroestl's bit slicing).

This weekend I'm planning to get more hashrate for both the "groestlcoin" and "optimized" kernels.

Once it is ready, I'll post here and in twitter (https://twitter.com/CryptoHunger).

Also, if you are mining on cryptohunger.com:5000X, you will see a notification message pop up.

Keep on hashing!

Thanks!
srcxxx
srcxxx
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250


View Profile WWW
June 27, 2014, 07:57:58 AM
 #124

@srcxxx

You asked why I am solo mining, As soon as my block gets confirmed it starts getting coin-age right?  Seems like an advantage over pool mining to me Smiley

Hi!

With a pool you'll be getting payouts every hour.
And the newly received coins will start accumulating coin age in your wallet every hour.

If you are solo mining, you don't get blocks on a regular basis.

Also, I doubt that a few more minutes of coin age will change much.

Plus there is additional hashrate in optimized kernel.

srcxxx
polanskiman
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
June 27, 2014, 09:02:55 AM
 #125

Hi Guys!

First of all, thanks for your feedback. Both positive and negative.

Regarding the pool and the lack of statistics...
As I already said, I would like to have statistics myself. Pools like http://max.1gh.com/ and http://dwarfpool.com/tac have nice statistics and stuff.
But they are using some custom pool code and it is not open source. I.e. I don't have access to it.

MPOS is open source and I even have it running on grs.cryptohunger.com. But... I hate it.
Had too many troubles with it (BTW, I had to write my own stratum implementation for Groestlcoin which took 2 weeks).
So I am not going to use MPOS.

When you are just starting mining or switching to a new coin, you want statistics. I get that. But once you played with it for a few days, you just leave your rigs hashing and find something else to occupy your time. Just look at the 1.13 GH whale mining Dokdocoin (BTW, thanks for staying on my pool, whoever you are). I'm sure he is very sensitive to the amount of coins he gets every hour.

NOMP is a new project. It is growing fast. It is very good conceptually (very low server load, no risk for pool operator as all coins are completely paid out). Just about a month ago it didn't have worker statistics. Now it is added: http://cryptohunger.com:81/workers
There is a feature request for statistics in NOMP and I'm hoping it'll be added shortly.

I encourage you to give it a try with the "optimized" kernel. Leave it running say overnight.
In the morning check transactions in your wallet. There will be some coins sent to you every hour. That's your statistics.
If you are happy with it - please keep mining.
If you are not - no problem also. Use some other pool with "groestlcoin" kernel.
Yes, the non-optimized kernel is slower. But it is still faster than the sph-sgminer.

I am planning to continue working on grs-sgminer until there is stuff to optimize (currently I see 5 potential changes that might improve hashrate, that is without completely changing the algo, like ccMiner KillerGroestl's bit slicing).

This weekend I'm planning to get more hashrate for both the "groestlcoin" and "optimized" kernels.

Once it is ready, I'll post here and in twitter (https://twitter.com/CryptoHunger).

Also, if you are mining on cryptohunger.com:5000X, you will see a notification message pop up.

Keep on hashing!

Thanks!
srcxxx


+1

"But once you played with it for a few days, you just leave your rigs hashing and find something else to occupy your time."
Yes and no. Yes you are right. No, it's not a reason for not actively persuing improvements. People might not look at the pool every day, still people are investing in your pool and the future of the coin.

In anycase, for me what should be addressed in priority is the looks of the website. At least make it look like it's finished. Like I said the API and the Get Started pages seem to be incomplete and that for me is more of a problem than the current available stats. It doesn't give a good image. I rather see something little but well finished than a huge gas factory where flames are coming out of everywhere whole. You get my point.

As for the stats, well I guess patience is the word. The basic stats I would personally like to see are:
- estimated coin/day
- hashing history of addresses under graph form
- node uptime
- current coin difficulty
- payouts per address (this would give some more transparency to the project)

Anyways, good job. Keep it coming. BTW is it your job to code?

BTC: 1JnH2HVoWnDubGmrXintsNWEaByGRjY8wL
DMD: dZuojpnwkmzqUegQaFk7ynDY8p7zAmG25H
XCN: CKnXnjXsVJzXgqEEqjsMRRc7ohkk6jHsb6
srcxxx
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250


View Profile WWW
June 27, 2014, 09:09:21 AM
 #126

I'm seeing lots of orphaned blocks on Diamond pool.

I'm pretty sure I'm on the right fork.

Quote
root@CryptoHunger:~# diamondd getinfo
{
    "version" : "v2.0.2.1",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "balance" : 148.69427000,


root@CryptoHunger:~# diamondd getcheckpoint
{
    "synccheckpoint" : "000000005babbddb5baad7bb9632738ab901b2f9eb3acfd2f390b2f4a97f1eee",
    "height" : 463183,
    "timestamp" : "2014-06-26 16:46:41 UTC"
}

I think it may influence payouts.
polanskiman
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
June 27, 2014, 09:15:14 AM
 #127

I'm seeing lots of orphaned blocks on Diamond pool.

I'm pretty sure I'm on the right fork.

Quote
root@CryptoHunger:~# diamondd getinfo
{
    "version" : "v2.0.2.1",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "balance" : 148.69427000,


root@CryptoHunger:~# diamondd getcheckpoint
{
    "synccheckpoint" : "000000005babbddb5baad7bb9632738ab901b2f9eb3acfd2f390b2f4a97f1eee",
    "height" : 463183,
    "timestamp" : "2014-06-26 16:46:41 UTC"
}

I think it may influence payouts.

Should I stop my miner?

BTC: 1JnH2HVoWnDubGmrXintsNWEaByGRjY8wL
DMD: dZuojpnwkmzqUegQaFk7ynDY8p7zAmG25H
XCN: CKnXnjXsVJzXgqEEqjsMRRc7ohkk6jHsb6
srcxxx
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250


View Profile WWW
June 27, 2014, 09:21:18 AM
 #128

> Anyways, good job. Keep it coming. BTW is it your job to code?

Thanks, I'm a professional C/C++ developer and specialize in 3D graphics.

As for the pool software... It's not really my thing.
I'm using what's available open source. NOMP is a community project here: https://github.com/zone117x/node-open-mining-portal
srcxxx
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250


View Profile WWW
June 27, 2014, 09:25:52 AM
 #129

I'm seeing lots of orphaned blocks on Diamond pool.

I'm pretty sure I'm on the right fork.

Quote
root@CryptoHunger:~# diamondd getinfo
{
    "version" : "v2.0.2.1",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "balance" : 148.69427000,


root@CryptoHunger:~# diamondd getcheckpoint
{
    "synccheckpoint" : "000000005babbddb5baad7bb9632738ab901b2f9eb3acfd2f390b2f4a97f1eee",
    "height" : 463183,
    "timestamp" : "2014-06-26 16:46:41 UTC"
}

I think it may influence payouts.

Should I stop my miner?

I don't think so. But it is your choice.

I think that the network is currently in a "not so good" state. And if you mine on a different pool, it'll probably be the same.

I guess I'm just saying that statistics may not look good for awhile.

I had similar problems with Groestlcoin when we hard-forked.
polanskiman
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
June 27, 2014, 09:36:19 AM
Last edit: July 01, 2014, 05:29:21 AM by polanskiman
 #130

I'm seeing lots of orphaned blocks on Diamond pool.

I'm pretty sure I'm on the right fork.

Quote
root@CryptoHunger:~# diamondd getinfo
{
    "version" : "v2.0.2.1",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "balance" : 148.69427000,


root@CryptoHunger:~# diamondd getcheckpoint
{
    "synccheckpoint" : "000000005babbddb5baad7bb9632738ab901b2f9eb3acfd2f390b2f4a97f1eee",
    "height" : 463183,
    "timestamp" : "2014-06-26 16:46:41 UTC"
}

I think it may influence payouts.

Should I stop my miner?

I don't think so. But it is your choice.

I think that the network is currently in a "not so good" state. And if you mine on a different pool, it'll probably be the same.

I guess I'm just saying that statistics may not look good for awhile.

I had similar problems with Groestlcoin when we hard-forked.

Ok. As long as the pool where people are mining is on the right fork then it should be ok...hopefully!.

BTC: 1JnH2HVoWnDubGmrXintsNWEaByGRjY8wL
DMD: dZuojpnwkmzqUegQaFk7ynDY8p7zAmG25H
XCN: CKnXnjXsVJzXgqEEqjsMRRc7ohkk6jHsb6
srcxxx
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250


View Profile WWW
June 27, 2014, 09:55:43 AM
 #131

Looks like the situation with DMD is ok now.

The number of orhpaned blocks is 228 and is not growing (http://cryptohunger.com:81/tbs).

I also checked the "getpeerinfo" and all nodes connected to the pool are 2.0.2.1.
polanskiman
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
June 27, 2014, 10:04:15 AM
 #132

Looks like the situation with DMD is ok now.

The number of orhpaned blocks is 228 and is not growing (http://cryptohunger.com:81/tbs).

I also checked the "getpeerinfo" and all nodes connected to the pool are 2.0.2.1.

Good to know. When you first noticed the increase in orphans, what was the number?

BTC: 1JnH2HVoWnDubGmrXintsNWEaByGRjY8wL
DMD: dZuojpnwkmzqUegQaFk7ynDY8p7zAmG25H
XCN: CKnXnjXsVJzXgqEEqjsMRRc7ohkk6jHsb6
sce
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
June 27, 2014, 11:20:06 AM
 #133

Hello,

I have problem with wallet and I donn't know what to do?

I get this message when I run it:

--------------------------------------------------------
MinGW Runtime Assertion
--------------------------------------------------------

Assertion failed!

......\Diamond v.2.0.2.1\diamond-qt.exe
File: src\kernel.cpp, Line 412

Expression: pindex- >pprev || pindex- >GetBlockHash() ==
(!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)


Does anyone have this kind a problem?
polanskiman
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
June 27, 2014, 11:33:13 AM
 #134

Hello,

I have problem with wallet and I donn't know what to do?

I get this message when I run it:

--------------------------------------------------------
MinGW Runtime Assertion
--------------------------------------------------------

Assertion failed!

......\Diamond v.2.0.2.1\diamond-qt.exe
File: src\kernel.cpp, Line 412

Expression: pindex- >pprev || pindex- >GetBlockHash() ==
(!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)


Does anyone have this kind a problem?

You would be better off posting in the official thread: https://bitcointalk.org/index.php?topic=580725.1480

That is an issue the wallet has been experiencing since yesterday. The blockchain forked. Most are having the same problem unless you keep your wallet open, which is not viable for me.

BTC: 1JnH2HVoWnDubGmrXintsNWEaByGRjY8wL
DMD: dZuojpnwkmzqUegQaFk7ynDY8p7zAmG25H
XCN: CKnXnjXsVJzXgqEEqjsMRRc7ohkk6jHsb6
polanskiman
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
June 27, 2014, 11:55:48 AM
Last edit: June 27, 2014, 12:23:45 PM by polanskiman
 #135

http://cryptohunger.com:81 seems to be down.

EDIT: Seems to be back up.

BTC: 1JnH2HVoWnDubGmrXintsNWEaByGRjY8wL
DMD: dZuojpnwkmzqUegQaFk7ynDY8p7zAmG25H
XCN: CKnXnjXsVJzXgqEEqjsMRRc7ohkk6jHsb6
Litejavichu
Hero Member
*****
Offline Offline

Activity: 690
Merit: 500



View Profile
June 27, 2014, 01:12:47 PM
 #136

The website looks great Cool Cool
incognitoworker
Hero Member
*****
Offline Offline

Activity: 736
Merit: 500


View Profile
June 27, 2014, 01:46:37 PM
 #137

when starting miner, i get an error 11, frontend error.
and miner crashes.
what have i done wrong? :-)
win 7, 64x  13.12 drivers with 4 280x gpus.

Quotient- Closed loop economy enviroment experiment
https://bitcointalk.org/index.php?topic=1195335.0
polanskiman
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
June 27, 2014, 05:20:11 PM
 #138

The website looks great Cool Cool


You mean the girl looks great  Tongue

BTC: 1JnH2HVoWnDubGmrXintsNWEaByGRjY8wL
DMD: dZuojpnwkmzqUegQaFk7ynDY8p7zAmG25H
XCN: CKnXnjXsVJzXgqEEqjsMRRc7ohkk6jHsb6
BusyBeee
Member
**
Offline Offline

Activity: 86
Merit: 10


View Profile
June 28, 2014, 01:38:35 AM
 #139

grs-sgminer is a OpenCL optimized miner for Groestlcoin, Diamondcoin coins.

Speed with Groestl mining:

R9 290 - 20 MH/s (14.4MH/s if using standard sph-sgminer with 14.6 beta AMD drivers and 9.5MH/s on drivers prior to 14.6)
R9 270X - 10 MH/s
R9 280X - 16 MH/s (some only report 12MH/s, see details below. Probably you need 13.12 driver)

Github: https://github.com/srcxxx/grs-sgminer
Twitter (to get updates on new versions): https://twitter.com/CryptoHunger


Version 1.2.5 (third release, 25 June 2014)
* Windows build
* Added R9 290 optimized Kernel for Tahiti, Pitcairn and Hawaii GPUs
* Shows a warning if "optimized" kernel is used with incorrect pool




Hi srcxxx, many thanks for sharing your work with the community.  Version 1.2.5 worked as expected on r9 290 and r9 280x with catalyst 14.4.  When I switch to catalyst 13.12, I get the "Error: Compilation from LLVMIR binary to IL text failed!."  What can I do to correct the problem?
polanskiman
Full Member
***
Offline Offline

Activity: 238
Merit: 100


View Profile
June 28, 2014, 03:30:01 AM
Last edit: June 30, 2014, 09:21:34 AM by polanskiman
 #140

Hello scrxxx,

I've updated grs-sgminer to 1.2.5 today. I am getting the following error if I use the .bop file provided in the 1.2.5 version. It does this while loading (I guess for each gpu thread) and then sgminer starts fine. Cards start hashing ok too exept they hash less than with the 1.2.4 .bop file.

Code:
Optimized groestlcoin kernel invoked.WARNING: Linking two modules of different data layouts!
                                                                                                       WARNING: Linking two modules of different target triples: 'amdil64-pc-unknown-amdopencl' and 'amdil-pc-unknown-amdopencl'
                                                                                                                                                                                                                                WARNING: Linking two modules of different data layouts!
                                                                                                                                                                                                                                                                                       WARNING: Linking two modules of different target triples: 'amdil64-pc-unknown-amdopencl' and 'amdil-pc-unknown-amdopencl'
                                                                                                                         WARNING: Linking two modules of different data layouts!
                                                                                                                                                                                WARNING: Linking two modules of different target triples: 'amdil64-pc-unknown-amdopencl' and 'amdil-pc-unknown-amdopencl'

BTC: 1JnH2HVoWnDubGmrXintsNWEaByGRjY8wL
DMD: dZuojpnwkmzqUegQaFk7ynDY8p7zAmG25H
XCN: CKnXnjXsVJzXgqEEqjsMRRc7ohkk6jHsb6
Pages: « 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 15 16 17 »  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!