Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - xolokram

Pages: 1 ... 9 10 11 12 13 14 15 [16]
226
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool!
« on: November 09, 2013, 11:00:49 am »
pool backend has a bug
the pool will be back in a few minutes
i'm working on it


(blocks&payouts are save)

ok i deployed a workaround, i'll look into that issue later today

/edit:

AND i fixed the hashrate counter fix (yes, i guess i need some sleep.......)
commithash = 48d62e8f95

227
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool!
« on: November 09, 2013, 09:21:48 am »
please use the "edit" button instead of double posting

if you are using v0.2 then everything should be fine

as long as you're also using:
-poolip=ptsmine.beeeeer.org -poolport=1337
 ;D

ps. i just pushed the hashrate counter fix (or i hope it's finally fixed now :) ) to github: linux users pull the latest source from github (commit = 48d62e8f95..)

228
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool!
« on: November 09, 2013, 09:14:35 am »
i just checked my logs on the pool, looks like there are no issues on my side currently (except for a restart on the web frontend sometime last night)
you should definitely switch to the new miner, the old one (incl. the original pts client) ist just bad regarding rejection rates (stale blocks)


btw if a payout states "reward = 0" (e.g. here), that specific block is an orphan unfortunately --- just fyi before someone asks
everyone who is/was mining on my old xpm pool should be aware of the gorgeous payout-info pages

- xolokram

229
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool!
« on: November 09, 2013, 09:03:41 am »
@LOW HASHRATE:
the console output is bugged, i missed the counter that is now skipped occasionally due to the rejection rate fix
the actual hash rate is just like before, nothing has changed in the mining code, except that the miner is now updated correctly, when the pool spreads new work to the miners
not like with v0.1, which was just mining on stale blocks

i will fix that with the next release (linux source code update on github in a few minutes now)
if someone is interested, i can show you this in the code @smith88 & feeleep & rando & co.

@64 BIT & xxrforone & lzr1900 & co.:
eta is about 11 hours on my side (i'm currently not on a windows machine) --- i think the other guy from the "nameless pool" (ptspool?) will be faster with compiling the miner today
but miners & pools are compatible (afaik)

you can already compile the miner for 64bit on linux machines, just use the common instructions for linux.
if you have a 64bit machine, a 64bit distribution, then you're compilation suite should be 64bit too and thus compile the 64bit version of the miner!

@LiteMine:
you're probably right - man, i hate this thread managing :) i need a PR manager :D

@donschoe:
like always, thx for the help

- xolokram

230
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool!
« on: November 09, 2013, 12:21:08 am »
the provided code hotfix can be used as "diff" for the source code (google)

- xolokram

ps. i'll be off for today, payout script should run when the first block is confirmed... good night
pps. ok, i just monitored the first 2 payouts, looks like everything is working fine --- i hope the pool will survive the night :)

231
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool!
« on: November 09, 2013, 12:02:23 am »
ah i just noticed (thx to defragger) that the hashrate counter is not adding the counter when a new block just came in before a result was calculated
thus the hashrate will be lower for v0.2 than v0.1 --- in other words: currently only finished mining iterations are considered in the hashrate calculation.

- xolokram

232
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool!
« on: November 08, 2013, 11:43:39 pm »
Is there a pool password?
no

the password option is there out of historical reasons

/edit: oh, thx hotapeno :)

233
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool!
« on: November 08, 2013, 11:41:46 pm »
64bit will take some time, because i'm currently not at my windows machine (and i'll have to adjust the compilation file first)
rough eta ~20 hours

just run multiple instances of the miner if you want to test the pool with more threads (yeah it's a ugly workaround)

- xolokram

234
BitShares PTS / Re: Mining Pool?
« on: November 08, 2013, 11:10:26 pm »

235
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool!
« on: November 08, 2013, 10:42:04 pm »
wait unitl i f--- up the payout script :D you remember the good ol' primecoin times.......  :o

btw. PLEASE DONT USE v0.1 MINER FROM THE OTHER "NAMELESS" POOL

get sure what version you use!!

236
BitShares PTS / [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool
« on: November 08, 2013, 10:34:43 pm »
Hi,

this is the official announcement for my protoshares mining sub-pool for www.beeeeer.org
i'm the guy who runs beeeeer.org (obviously)

SERVICE HAS BEEN SHUT DOWN
thanks to all supporters

Some stats/features:
  • 2.5% fee
  • no registration needed, username is your protoshares-address
  • beta testing phase (i'll work on every little bug/problem ASAP)
  • custom protocol & miner (based on ptspool miner based on my xpm miner)
  • i'm currently working on the payout system, at the moment it's proportional  (but this will change)
  • your payout will be executed, when blocks are confirmed (delay of 120 blocks) and you reach 0.1 PTS
  • high end visual stunning plain-text web interface

Link:
ptsweb.beeeeer.org <-- for your browser / see mining below

Client / Miner:

linux / github: source code here
windows binary: v0.5 x32 HOTFIX-1 -> ptsminer_v05a_x32.zip (32 Bit, fast™!) up to 3 threads
windows binary: v0.5 x64 HOTFIX-1 -> ptsminer_v05a_x64.zip (64 Bit, faster™!!)
windows binary: v0.7 x64 RC1 -> ptsminer_v07b_x64.zip (64 Bit, AVX/SSE/SPHLIB experimental, fastererer™!!!) *UPDATED-#3* incl. 'rejections-on-a-block-workaround-by-reconnecting'-fix
(containing GENERIC (INTEL&AMD) , SSE4 and AVX version (INTEL&AMD))

mac: try http://bitsharestalk.org/index.php?topic=234.msg3904#msg3904 (thx to spoonman)

build notes: compilation needs boost lib & yasm

some notes:
a) it's not possible to completely erase the rejection rate problem (especially at the current low blocktime)
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 use the amount of submitted valid shares per hour (or similiar) regarding mining performance
c) i'll look into the occasional random crashs next... give me some time
d) "b" applies for v0.5 and higher too :)

v0.4 or lower
Code: [Select]
usage:
ptsminer -poolip=<_SHUT_DOWN_> -poolport=1337 -pooluser=<your-pts-payout-address> -genproclimit=<threads-to-use>
example:
ptsminer -poolip=<_SHUT_DOWN_> -poolport=1337 -pooluser=PbfspbvSWxYqrp3DpRH7bsrmEqzY3418Ap -genproclimit=4

v0.5
Code: [Select]
usage:
ptsminer <your-pts-payout-address> <threads-to-use>
example:
ptsminer PbfspbvSWxYqrp3DpRH7bsrmEqzY3418Ap 4

v0.6
github only

v0.7
Code: [Select]
choose <version> depending on your CPU and mining implementation you want to use

usage: ptsminer_<version>.exe <payout-address> <threads-to-use> [memory-option] [mode]

memory-option: integer value - memory usage
                20 -->    4 MB per thread (not recommended)
                21 -->    8 MB per thread (not recommended)
                22 -->   16 MB per thread (not recommended)
                23 -->   32 MB per thread (not recommended)
                24 -->   64 MB per thread (not recommended)
                25 -->  128 MB per thread
                26 -->  256 MB per thread
                27 -->  512 MB per thread (default)
                28 --> 1024 MB per thread
                29 --> 2048 MB per thread
                30 --> 4096 MB per thread

mode: string - mining implementation
                avx --> use AVX (ptsminer_avx.exe)
                sse4 --> use SSE4 (ptsminer_avx.exe & ptsminer_sse4.exe)
                sph --> use SPHLIB (ptsminer_avx.exe, ptsminer_sse4.exe, ptsminer_amd.exe & ptsminer_intel.exe)


examples:
ptsminer_avx.exe PbfspbvSWxYqrp3DpRH7bsrmEqzY3418Ap 4
using AVX on 4 threads and 512 MByte RAM per thread (default)

ptsminer_sse4.exe PbfspbvSWxYqrp3DpRH7bsrmEqzY3418Ap 8 28
using SSE4 on 8 threads and 1024 MByte RAM per thread

ptsminer_intel.exe PbfspbvSWxYqrp3DpRH7bsrmEqzY3418Ap 2 25 sph
using SPHLIB on 2 threads and 128 MByte RAM per thread

ptsminer_avx.exe PbfspbvSWxYqrp3DpRH7bsrmEqzY3418Ap 12 24 sph
using SPHLIB on 12 threads and 64 MByte RAM per thread

FAQ:

Quote
We are not responsible for any damage to your computer system or data with our provided
service and software and in no event will we be responsible for any consequential, incidental,
or indirect damages arising out of the use or inability to use our service or software.

Any known issues?
not by now

Why 'beeeeer.org'?
Everybody loves beer, that's why. (Ok, almost everybody)

Has the server crashed again?
If the status page isn't available: yup - something really bad happened. We're still in beta/testing phase, don't panic, everything will be ok!!

AVX instruction set on Amazon EC2:
Quote
AVX instructions are supported only when HVM virtualization is used. There are HVM versions of the Amazon Linux AMI and Ubuntu AMI available. Unfortunately AVX cannot be used with a PV Linux AMI due to incompatibilities with some Linux kernels regarding XSAVE instructions.

A list of HVM Amazon Linux AMI IDs is available here: http://aws.amazon.com/amazon-linux-ami/

- xolokram, glhf

wanna donate?
BTC: 1S4kxaF4ro17qThUz4hQwAoiXzCWdzwdb
LTC: LMgYASNbAgGUG6fhw1xdMAWSbMiWjNNGgo
XPM: AJhA1PGbNM94ZmsJvVVM5FfbE9SdxiMzgd
PTS: PbfspbvSWxYqrp3DpRH7bsrmEqzY3418Ap

just fyi: i'll fix that asap...
ah i just noticed (thx to defragger) that the hashrate counter is not adding the counter when a new block just came in before a result was calculated
thus the hashrate will be lower for v0.2 than v0.1 --- in other words: currently only finished mining iterations are considered in the hashrate calculation.

- xolokram

/APPENDIX: here's a fix (someone said bounty??) for the original protoshares client to increase the solo mining performance...
nvm, nobody cares

237
General Discussion / Re: $2000 Bounty - ProtoShares Mining Pool [CANCELED]
« on: November 08, 2013, 04:01:22 pm »
donate some pts to xolo, thanks!
thank you, I appreciate it.

238
General Discussion / Re: $2000 Bounty - ProtoShares Mining Pool [CANCELED]
« on: November 08, 2013, 11:54:08 am »
...
you[...]r [...] awesome, thanks xolokram[...]

Change kh/s to hp/m...and donate some pts to xolo  :o
thank you.

if someone really feels the generous urge: PTS @ PbfspbvSWxYqrp3DpRH7bsrmEqzY3418Ap

- xolokram

239
General Discussion / Re: $2000 Bounty - ProtoShares Mining Pool [CANCELED]
« on: November 08, 2013, 08:55:28 am »
yep, they're using parts of my sourcecode for their miner.
thx for the credits ... oh wait ...

Pages: 1 ... 9 10 11 12 13 14 15 [16]