[ANN] Restart of Quantumcoin (SUCCESSFULLY RELEASED)

[Sondey10mg]

Yes, best release I have seen since I joined the board begin of april

[Sikon024]

Im getting 60/40 Acc to rejects on the pool. Anyone else?

[tyrion70]

Grr:

Code:

2013-06-06 21:52:31.282851 > exceptions.NameError: global name 'exp' is not defined

Apparently exp is not a valid python function..

@Sikon my stats from when I started the pool:

Code:

 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0:  72.0C 4056RPM | 388.3K/359.8Kh/s | A:392 R:268 HW:0 U:  6.58/m I:19
 GPU 1:  72.0C  26%    | 169.8K/173.2Kh/s | A:109 R:193 HW:0 U:  1.83/m I:19
 GPU 2:  73.0C  69%    | 169.9K/173.2Kh/s | A:101 R:190 HW:0 U:  1.70/m I:19

I just reset my statistics to see how it's now. It usually takes p2pool some time to get the share diff at a good level. Have u got your scan and expiry time at 1?

Code:

[Q]ueue: 0
[S]cantime: 1
[E]xpiry: 1

EDIT:
My scan and exp setting were wrong to... lol

Anyways since reset it looks like this:

Code:

 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0:  73.0C 3761RPM | 390.3K/343.8Kh/s | A: 12 R:  1 HW:0 U:  3.09/m I:19
 GPU 1:  73.0C  23%    | 182.5K/166.3Kh/s | A:  6 R:  3 HW:0 U:  1.54/m I:19
 GPU 2:  74.0C  60%    | 182.4K/166.3Kh/s | A:  6 R:  2 HW:0 U:  1.54/m I:19

Where most rejects seem to come from the fact that my cards sometimes find a share at the same time.

[rabidwalrus]

Im getting 60/40 Acc to rejects on the pool. Anyone else?

I'm getting about 10%

[tyrion70]

Just restarted the pool to implement the correct subsidy function..

Code:

Total block value: 10.438951

sounds a lot better..

for the record, this is the bitcoin/networks.py part involved:

Code:

def get_subsidy(bnTarget):
    import math
    return int(((0.2 * math.exp(bnTarget/ 250) / pow(bnTarget, -0.25)) * 50) * 1000000)

nets = dict(
    quantumcoin=math.Object(
        SUBSIDY_FUNC=lambda target: get_subsidy(target),
    ),

Cheers

[MaGNeT]

I like this coin and it's release

I only mined 3 blocks and I'm back on PXC but it was a fair launch

[cryptohunter]

agree with this, excellent launch.

[Sikon024]

Grr:

Code:

2013-06-06 21:52:31.282851 > exceptions.NameError: global name 'exp' is not defined

Apparently exp is not a valid python function..

@Sikon my stats from when I started the pool:

Code:

 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0:  72.0C 4056RPM | 388.3K/359.8Kh/s | A:392 R:268 HW:0 U:  6.58/m I:19
 GPU 1:  72.0C  26%    | 169.8K/173.2Kh/s | A:109 R:193 HW:0 U:  1.83/m I:19
 GPU 2:  73.0C  69%    | 169.9K/173.2Kh/s | A:101 R:190 HW:0 U:  1.70/m I:19

I just reset my statistics to see how it's now. It usually takes p2pool some time to get the share diff at a good level. Have u got your scan and expiry time at 1?

Code:

[Q]ueue: 0
[S]cantime: 1
[E]xpiry: 1

EDIT:
My scan and exp setting were wrong to... lol

Anyways since reset it looks like this:

Code:

 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0:  73.0C 3761RPM | 390.3K/343.8Kh/s | A: 12 R:  1 HW:0 U:  3.09/m I:19
 GPU 1:  73.0C  23%    | 182.5K/166.3Kh/s | A:  6 R:  3 HW:0 U:  1.54/m I:19
 GPU 2:  74.0C  60%    | 182.4K/166.3Kh/s | A:  6 R:  2 HW:0 U:  1.54/m I:19

Where most rejects seem to come from the fact that my cards sometimes find a share at the same time.

Much better.  The getwork efficiency in CGwatcher is ugly but with a coin that changes this fast, ya gotta do whacha gotta do.

Thank you!

[Lhunephel]

Added two checkpoints to the sources on GitHub.

[Lhunephel]

@tyrion70: Is your p2pool at http://qtc.p2pool.nl/stats/ not working? Can't see the last blocks and the statistics are also not working

[tyrion70]

@tyrion70: Is your p2pool at http://qtc.p2pool.nl/stats/ not working? Can't see the last blocks and the statistics are also not working

Hmm seems to be working here:

Code:

393406	Fri Jun 07 2013 11:54:45 GMT+0200 (West-Europa (zomertijd))	758b727c83164ca2715e09b20c9874294ecc0412775858a5d5607124a629858a
393404	Fri Jun 07 2013 11:03:37 GMT+0200 (West-Europa (zomertijd))	2c71bb685af85ca26234a7eb6703f818ae5d2797a175e19f69988e2194f43596
393403	Fri Jun 07 2013 10:38:29 GMT+0200 (West-Europa (zomertijd))	dcd92479021b5b7258c1887c0804484bf9612a7d01e38a25fa8a6d6a784b3156
393402	Fri Jun 07 2013 10:28:30 GMT+0200 (West-Europa (zomertijd))	23ac3481742e9e0e4bfeb359d72cd5ba9dfb845279f48314987624c96731435c
393401	Fri Jun 07 2013 10:26:58 GMT+0200 (West-Europa (zomertijd))	24a8db9c36a2efed8b833e8ee9d57c9879ff49f711e86ce04a90f581b5f6127d
393399	Fri Jun 07 2013 09:47:46 GMT+0200 (West-Europa (zomertijd))	2cec2ffbbb0d63800802b20948637d03d0acc8ab694a87412d608ad12a6ecbd2
393398	Fri Jun 07 2013 09:41:39 GMT+0200 (West-Europa (zomertijd))	7d0999ee80d028e82932e56cf2244d4a2d17d72e753206f97200b856b2ffe8a4

Tested it on my iPad and computer...

[Lhunephel]

Looks good now. I think I had some issues with my connection resulting in a broken statistics page.

[Boxman90]

Lol I had a fair amount of quantumcoins but then the dev says "Meh reboot". Sure. Is this one dead yet?

[tyrion70]

Looks good now. I think I had some issues with my connection resulting in a broken statistics page.

It's all XMLhttp.. It doesn't seem to work well on older browsers and buggy connections :d At work I can't read the stats very well either

[Lhunephel]

Because the first release of QTC really failed I decided to try it with a clean restart. That's what just happened. And I think the block chain had a really good restart and is working like expected. The old block chain is dead. Fetch the latest sources from GitHub or download the latest Windows binary to join the new and active block chain.

[Lhunephel]

@tyrion70: But I think there's something wrong with the displayed retarget interval. The maximum retarget interval is 15. Also I think the target spacing is not 60 seconds at the moment. Have a look in the sources (quantumcoin/src/main.cpp), there are three methods calculating the retarget, target spacing and target timespan parameters. I think the p2pool code has to be modified like with the block values.

[tyrion70]

@tyrion70: But I think there's something wrong with the displayed retarget interval. The maximum retarget interval is 15. Also I think the target spacing is not 60 seconds at the moment. Have a look in the sources (quantumcoin/src/main.cpp), there are three methods calculating the retarget, target spacing and target timespan parameters. I think the p2pool code has to be modified like with the block values.

You're right; I used the wrong spacing and interval params; same as with the subsidy.. But those values are really only used for statistic purposes. I'll take a look at them over the weekend.

Cheers

[Lhunephel]

At the moment the hash rate is too low for the block chain to work like expected

[Petr1fied]

That probably goes to prove that although people say they want a fair release with a difficulty of 1.0 so that it's not an orphanfest they don't actually mean it. What they really want is to mine when it's very easy so they can find lots of blocks. They just don't want the orphans that go hand in hand with that.

[ShowerFarts]

I tried. I threw my modest 1000 Khash at it until the client would no longer sync. I did think it was weird near the end when I was finding all of the blocks and there were no new blocks detected on the network. RIP quantumcoin.