[ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool

Started by xolokram, November 08, 2013, 10:34:43 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

hasher

[STATS] 2013-11-10 16:49:08 | hashmeter 3.671844 hashs/min
VL: 15 (100.0%), RJ: 0 (0.0%), ST: 0 (0.0%)
force reconnect if possible!
Found Hash 08706674d8ab1f5bd04cfdd2de027397c88c7560a5bc56a63f1661f91e580371
Segmentation fault

why it stopped? im doing somwthing wrong?

5chdn

Quote from: albon on November 10, 2013, 04:00:35 PM
is there any way to see your ballance?

go to latest payout http://ptsweb.beeeeer.org/payout/11873
hit ctrl+f search for your address until you find it in block "next" or "payout".

payout = your pts are sent to you and your balance is 0.
next = your balance if not paid out.

albon

PTS PZcyCXhyE2h8SK11Ed8Wg1WeuzwtVVeYCT

BTC 1BHPjHubNKQit9s8twvVmZVPdaF8RumFzB

xolokram

no, everything will be ok (hopefully, i updated the backend)
you dont have to update anything (but i recommend to use miner v0.4, if you've not switched yet)

@Nick:
thanks for the hint, i'll update the payout script & payouts
it looks like he's not mining currently

- xolokram

ps. i'll be back later today --- cross your fingers for the chainfork everyone
stats for [email protected]
BTC: 1S4kxaF4ro17qThUz4hQwAoiXzCWdzwdb | LTC: LMgYASNbAgGUG6fhw1xdMAWSbMiWjNNGgo
XPM: AJhA1PGbNM94ZmsJvVVM5FfbE9SdxiMzgd | PTS: PbfspbvSWxYqrp3DpRH7bsrmEqzY3418Ap

vortexfoto

xolokram, ive received emergency fork for protoshares, will we also have to change the client?

original mail:

Please download the new clients at:
http://invictus-innovations.com/downloads

All news announcement about this upgrade will be in the following topic:
http://bitsharestalk.org/index.php?topic=370.0

Regards,
The BitShares Forum Team.

http://bitsharestalk.org/index.php

Riverhead


New client is working great!  Compiled the source for my Linux i5 and it's running well too.  Thanks for all your hard work!  Was getting 80% rejects before but with your new miner it's happy days :).  Just got payed out at the 1PTS threshold so all is well for me.

Stats for 7 threads on an FX-8350 (one thread reserved for cgminer).

[STATS] 2013-11-10 15:15:33 | hashmeter 9.616751 hashs/min
VL: 119 (93.7%), RJ: 8 (6.3%), ST: 0 (0.0%)

Cheers.

Nick

You should probably implement a primitive autocorrect for payout addresses.
There is a guy out there with the address PmVC1BTpq6AcDFwAKC6PPtMEiTdGWhvhnn]

xolokram

BACKEND UPDATE INCOMING, POOL WILL BE DOWN FOR A FEW MINUTES DONE

- xolokram

ps. sorry for double post
stats for [email protected]
BTC: 1S4kxaF4ro17qThUz4hQwAoiXzCWdzwdb | LTC: LMgYASNbAgGUG6fhw1xdMAWSbMiWjNNGgo
XPM: AJhA1PGbNM94ZmsJvVVM5FfbE9SdxiMzgd | PTS: PbfspbvSWxYqrp3DpRH7bsrmEqzY3418Ap

xolokram

if you use ptsminer you dont have to update anything (except switching to v0.4 :) what i recommend )
i'll update the backend in a few minutes (this means a short downtime for the pool!) to be ready for the chainfork

- xolokram
stats for [email protected]
BTC: 1S4kxaF4ro17qThUz4hQwAoiXzCWdzwdb | LTC: LMgYASNbAgGUG6fhw1xdMAWSbMiWjNNGgo
XPM: AJhA1PGbNM94ZmsJvVVM5FfbE9SdxiMzgd | PTS: PbfspbvSWxYqrp3DpRH7bsrmEqzY3418Ap

bytemaster

Just wanted you all to be prepared to updated your client in the next couple of hours for the hard fork to address difficulty scaling.

We are in the final stages of testing it, but the code is already in github. 
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

xolokram

it takes ~4 minutes until the hashrate stats will appear
(before that it will just gather the data and displays 0 hashes/min)
stats for [email protected]
BTC: 1S4kxaF4ro17qThUz4hQwAoiXzCWdzwdb | LTC: LMgYASNbAgGUG6fhw1xdMAWSbMiWjNNGgo
XPM: AJhA1PGbNM94ZmsJvVVM5FfbE9SdxiMzgd | PTS: PbfspbvSWxYqrp3DpRH7bsrmEqzY3418Ap

max

hashmeter shows 0, but shares are getting submitted and accepted ok
(it just took a few shares before showed up)

max

updating now, thanks for your work!  ;)

no crashes here btw

xolokram

Hi,

my ptsminer v0.4 "next try hotfix"

Client / Miner:

linux / mac / github: source code here
windows binary: ptsminer_v04_x32.zip (32 Bit, supports up to 3 threads due to 32bit limitation)
windows binary: ptsminer_v04_x64.zip (64 Bit - more threads & faster!!)

usage:
ptsminer -poolip=ptsmine.beeeeer.org -poolport=1337 -pooluser=[your-payout-address] -genproclimit=[threads-to-use]

website:
ptsweb.beeeeer.org

some notes: !!! please read !!!
a) it's not possible to completely erase the rejection rate problem (especially at the current insane blocktime), but the patch/hotfix should reduce the problems!!
b) important: i changed the hashrate counter to count only valid iterations of the mining process (which v0.1, 0.2 & 0.3, and propably alpha miner? don't do!!!), thus your displayed hashrate is lower now --- but due to the changes i made for the rejection rate the miner is more effictive --- long story short: please only compare v0.4 against v0.4+ or the amount of submitted valid shares per hour (or similiar) regarding mining performance
c) i've added some changes to the MacOSX compilation file, can someone test if this works now? (i dont have a suitable test environment) macosx fix incoming
d) i'll look into the occasional random crashs next... give me some time

- xolokram

ps. there will be some downtime of the pool for a few minutes (in a few minutes) as i have to update the backend for the blockchain fork...
pps. i'm sorry about the inconvenience the last patch caused
stats for [email protected]
BTC: 1S4kxaF4ro17qThUz4hQwAoiXzCWdzwdb | LTC: LMgYASNbAgGUG6fhw1xdMAWSbMiWjNNGgo
XPM: AJhA1PGbNM94ZmsJvVVM5FfbE9SdxiMzgd | PTS: PbfspbvSWxYqrp3DpRH7bsrmEqzY3418Ap

montecristo83

Hi, I'm pretty new to this.

Have been running this for a while using 2 desktops. On the weakest one I'm getting mostly "REJECTED" shares. I suppose this is normal.

Is there a log file or similar that displays total results on the individual desktops?