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 - Clark

Pages: 1 [2]
16
BitShares PTS / About PTSPool's miner
« on: November 24, 2013, 05:51:29 am »
The pool, as listed in the topic: "Mining pool list - Updating",
PTSPool:
web:54.238.185.113

Its miner on github goes to the miner of beeeeer pool. Is it strange?
I try to compile it, then when running, the parameter of PTSPool can't be used.
It's beeeeer's miner.

So where is PTSPool's miner?
Thank you!

17
BitShares PTS / Re: Coyote Pool 2.0 - One Day Rounds Proportional Payout
« on: November 23, 2013, 09:41:43 am »
Why no source code for linux?
This binary can't work for me.

Code: [Select]
./linux_coyote_miner.0.3.0: /lib64/libc.so.6: version `GLIBC_2.17' not found (required by ./linux_coyote_miner.0.3.0)
./linux_coyote_miner.0.3.0: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./linux_coyote_miner.0.3.0)
./linux_coyote_miner.0.3.0: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by ./linux_coyote_miner.0.3.0)
./linux_coyote_miner.0.3.0: /usr/lib64/libstdc++.so.6: version `CXXABI_1.3.5' not found (required by ./linux_coyote_miner.0.3.0)
./linux_coyote_miner.0.3.0: /usr/lib64/libcrypto.so.1.0.0: no version information available (required by ./linux_coyote_miner.0.3.0)

18
nearly 6 hours without block found!

Is there anything wrong?


Just paid, was a very big block by the looks of things

24378 2013-11-23 07:28:21 2556 / 1533736 -> 0.04437 PTS / 26.62 PTS -> block waiting for confirmations

got that. Really big.
But I thought maybe the decrease of pool's workers cause the pool, as a whole, become weak.
So we have to wait long time for a block.

Am I right? Just become a miner for two days.

19
nearly 6 hours without block found!

Is there anything wrong?

Maybe I will move to another pool since I have no patience now.

Besides, I test v0.7 on Suse 11. It proves to be very useful.
And I have more memory to use, 8G per core. Can you offer a optimizaiton for this situation?

The 0.6 version of yasm is too old.
Then I test yasm v1.2. It's OK.
So, you can add this issue to help others.

Pages: 1 [2]