Bitcoin Forum
May 23, 2018, 08:18:10 AM *
News: Latest stable version of Bitcoin Core: 0.16.0  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 [7] 8 9 10 11 »  All
  Print  
Author Topic: [ANN][YAC] YAC Simple Pool [LP]  (Read 15817 times)
e521
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
May 10, 2013, 12:58:52 PM
 #121

anyone else getting high reject rates?
14/50 atm

with http://mineyac.dontmine.me:8080 server

no, 2945/3172 (92.84%)

You should make an announcement on altcoinforum.org!

is this spam going to end up anytime soon? -_-

1527063490
Hero Member
*
Offline Offline

Posts: 1527063490

View Profile Personal Message (Offline)

Ignore
1527063490
Reply with quote  #2

1527063490
Report to moderator
1527063490
Hero Member
*
Offline Offline

Posts: 1527063490

View Profile Personal Message (Offline)

Ignore
1527063490
Reply with quote  #2

1527063490
Report to moderator
1527063490
Hero Member
*
Offline Offline

Posts: 1527063490

View Profile Personal Message (Offline)

Ignore
1527063490
Reply with quote  #2

1527063490
Report to moderator
If you want to be a moderator, report many posts with accuracy. You will be noticed.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
sairon
Sr. Member
****
Offline Offline

Activity: 406
Merit: 250


One does not simply mine Bitcoins


View Profile
May 10, 2013, 01:00:34 PM
 #122

I wonder if it matters that I'm running my desktop-miner in a VM (other than the usual overhead-cost from the VM). Does the compiler accurately pick up what the native architecture is?

Why do you mine in a VM? Cheesy

GPG key ID: 5E4F108A || BTC: 1hoardyponb9AMWhyA28DZb5n5g2bRY8v
Rannasha
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
May 10, 2013, 01:01:48 PM
 #123

I wonder if it matters that I'm running my desktop-miner in a VM (other than the usual overhead-cost from the VM). Does the compiler accurately pick up what the native architecture is?

Why do you mine in a VM? Cheesy

Don't have Linux on my desktop as I use a number of Windows-only programs (= games). I'm not a very dedicated miner ^^ My laptop runs Linux natively, since it is my OS of choice.
gubb3l
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
May 10, 2013, 01:02:24 PM
 #124

I wonder if it matters that I'm running my desktop-miner in a VM (other than the usual overhead-cost from the VM). Does the compiler accurately pick up what the native architecture is?

Why do you mine in a VM? Cheesy

because actuall i´m under windows and i is the simplest way to get linux running on my maschine Wink
paul21
Member
**
Offline Offline

Activity: 70
Merit: 10


View Profile
May 10, 2013, 01:06:32 PM
 #125

The block chain keeps forking and then leaving a string of blocks as orphan. The blocks get 20+ confirms and then orphan.

Can you try:
addnode=67.162.14.58
addnode=72.8.182.2

To your yacoin.conf

The server has 24+ connections but I'm going to setup some other nodes to connect to it (don't want to publish the IP until I have the backups in place)

RIP my old pools... sometimes BTC isn't life ;(
Neverest
Jr. Member
*
Offline Offline

Activity: 56
Merit: 0



View Profile
May 10, 2013, 01:10:19 PM
 #126

I am also getting lots of stales (running under windows):

Biggest problem is connection, it seems?

Quote
[2013-05-10 09:53:10] thread 3: 73641 hashes, 4.50 khash/s
[2013-05-10 09:53:10] thread 2: 226694 hashes, 12.62 khash/s
[2013-05-10 09:53:23] HTTP request failed: Operation timed out after 30997 milli
seconds with 0 out of -1 bytes received
[2013-05-10 09:53:23] submit_upstream_work json_rpc_call failed
[2013-05-10 09:53:23] ...retry after 30 seconds
[2013-05-10 09:54:09] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 09:54:09] submit_upstream_work json_rpc_call failed
[2013-05-10 09:54:09] ...retry after 30 seconds
[2013-05-10 09:54:54] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 09:54:54] submit_upstream_work json_rpc_call failed
[2013-05-10 09:54:54] ...retry after 30 seconds
[2013-05-10 09:55:40] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 09:55:40] submit_upstream_work json_rpc_call failed
[2013-05-10 09:55:40] ...retry after 30 seconds
[2013-05-10 09:56:25] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 09:56:25] submit_upstream_work json_rpc_call failed
[2013-05-10 09:56:25] ...retry after 30 seconds
[2013-05-10 09:57:11] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 09:57:11] submit_upstream_work json_rpc_call failed
[2013-05-10 09:57:11] ...retry after 30 seconds
[2013-05-10 09:57:56] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 09:57:56] submit_upstream_work json_rpc_call failed
[2013-05-10 09:57:56] ...retry after 30 seconds
[2013-05-10 09:58:27] accepted: 1/2 (50.00%), 62.64 khash/s (booooo)
[2013-05-10 09:58:28] accepted: 1/3 (33.33%), 62.64 khash/s (booooo)
[2013-05-10 09:58:28] Long-polling activated for http://mineyac.dontmine.me:8080
/LP
[2013-05-10 09:58:29] thread 7: 15488 hashes, 12.84 khash/s
[2013-05-10 09:58:32] thread 4: 49551 hashes, 12.89 khash/s
[2013-05-10 09:58:33] thread 2: 59501 hashes, 12.36 khash/s
[2013-05-10 09:58:39] accepted: 2/4 (50.00%), 86.34 khash/s (yay!!!)
[2013-05-10 09:58:40] accepted: 3/5 (60.00%), 86.34 khash/s (yay!!!)
[2013-05-10 09:58:43] LONGPOLL detected new block
[2013-05-10 09:58:43] thread 1: 143056 hashes, 9.54 khash/s
[2013-05-10 09:58:43] thread 3: 175437 hashes, 11.73 khash/s
[2013-05-10 09:58:43] thread 4: 61098 hashes, 13.12 khash/s
[2013-05-10 09:58:43] thread 0: 62878 hashes, 4.19 khash/s
[2013-05-10 09:58:43] thread 6: 19530 hashes, 1.31 khash/s
[2013-05-10 09:58:43] thread 2: 20946 hashes, 6.34 khash/s
[2013-05-10 09:58:43] thread 5: 167487 hashes, 11.17 khash/s
[2013-05-10 09:58:48] LONGPOLL detected new block
[2013-05-10 09:58:48] thread 4: 64145 hashes, 12.74 khash/s
[2013-05-10 09:58:43] thread 7: 14634 hashes, 3.14 khash/s
[2013-05-10 09:58:49] thread 0: 67879 hashes, 12.96 khash/s
[2013-05-10 09:58:49] thread 5: 248 hashes, 13.78 khash/s
[2013-05-10 09:58:49] thread 1: 68157 hashes, 12.78 khash/s
[2013-05-10 09:58:49] thread 3: 66818 hashes, 12.54 khash/s
[2013-05-10 09:58:49] thread 6: 8049 hashes, 3.38 khash/s
[2013-05-10 09:58:49] thread 2: 283 hashes, 13.48 khash/s
[2013-05-10 09:58:50] thread 4: 12376 hashes, 10.36 khash/s
[2013-05-10 09:58:55] thread 5: 77115 hashes, 12.25 khash/s
[2013-05-10 09:59:07] thread 0: 223817 hashes, 12.16 khash/s
[2013-05-10 09:59:11] thread 4: 69679 hashes, 3.39 khash/s
[2013-05-10 09:59:19] thread 1: 366488 hashes, 12.21 khash/s
[2013-05-10 09:59:21] HTTP request failed: Operation timed out after 30046 milli
seconds with 0 out of -1 bytes received
[2013-05-10 09:59:21] submit_upstream_work json_rpc_call failed
[2013-05-10 09:59:21] ...retry after 30 seconds
[2013-05-10 09:59:27] thread 7: 188370 hashes, 4.93 khash/s
[2013-05-10 09:59:42] thread 6: 199715 hashes, 3.78 khash/s
[2013-05-10 09:59:42] thread 3: 407517 hashes, 7.66 khash/s
[2013-05-10 09:59:47] thread 5: 661684 hashes, 12.65 khash/s
[2013-05-10 09:59:53] thread 2: 795058 hashes, 12.50 khash/s
[2013-05-10 09:59:54] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 10:00:06] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 10:00:06] submit_upstream_work json_rpc_call failed
[2013-05-10 10:00:06] ...retry after 30 seconds
[2013-05-10 10:00:52] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 10:00:52] submit_upstream_work json_rpc_call failed
[2013-05-10 10:00:52] ...retry after 30 seconds
[2013-05-10 10:01:37] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 10:01:37] submit_upstream_work json_rpc_call failed
[2013-05-10 10:01:37] ...retry after 30 seconds
[2013-05-10 10:02:23] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 10:02:23] submit_upstream_work json_rpc_call failed
[2013-05-10 10:02:23] ...retry after 30 seconds
[2013-05-10 10:03:08] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 10:03:08] submit_upstream_work json_rpc_call failed
[2013-05-10 10:03:08] ...retry after 30 seconds
[2013-05-10 10:03:54] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 10:03:54] submit_upstream_work json_rpc_call failed
[2013-05-10 10:03:54] ...retry after 30 seconds

Etc.
It this because of ddos?

20 years of crypto/Digicash experience. BTC: 1CHCSdHZj9Umcek2wKkwzRTB3rLkUb8yma
paul21
Member
**
Offline Offline

Activity: 70
Merit: 10


View Profile
May 10, 2013, 01:12:38 PM
 #127

I am also getting lots of stales (running under windows):

Biggest problem is connection, it seems?

Quote
[2013-05-10 09:53:10] thread 3: 73641 hashes, 4.50 khash/s
[2013-05-10 09:53:10] thread 2: 226694 hashes, 12.62 khash/s
[2013-05-10 09:53:23] HTTP request failed: Operation timed out after 30997 milli
seconds with 0 out of -1 bytes received
[2013-05-10 09:53:23] submit_upstream_work json_rpc_call failed
[2013-05-10 09:53:23] ...retry after 30 seconds
[2013-05-10 09:54:09] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 09:54:09] submit_upstream_work json_rpc_call failed
[2013-05-10 09:54:09] ...retry after 30 seconds
[2013-05-10 09:54:54] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 09:54:54] submit_upstream_work json_rpc_call failed
[2013-05-10 09:54:54] ...retry after 30 seconds
[2013-05-10 09:55:40] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 09:55:40] submit_upstream_work json_rpc_call failed
[2013-05-10 09:55:40] ...retry after 30 seconds
[2013-05-10 09:56:25] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 09:56:25] submit_upstream_work json_rpc_call failed
[2013-05-10 09:56:25] ...retry after 30 seconds
[2013-05-10 09:57:11] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 09:57:11] submit_upstream_work json_rpc_call failed
[2013-05-10 09:57:11] ...retry after 30 seconds
[2013-05-10 09:57:56] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 09:57:56] submit_upstream_work json_rpc_call failed
[2013-05-10 09:57:56] ...retry after 30 seconds
[2013-05-10 09:58:27] accepted: 1/2 (50.00%), 62.64 khash/s (booooo)
[2013-05-10 09:58:28] accepted: 1/3 (33.33%), 62.64 khash/s (booooo)
[2013-05-10 09:58:28] Long-polling activated for http://mineyac.dontmine.me:8080
/LP
[2013-05-10 09:58:29] thread 7: 15488 hashes, 12.84 khash/s
[2013-05-10 09:58:32] thread 4: 49551 hashes, 12.89 khash/s
[2013-05-10 09:58:33] thread 2: 59501 hashes, 12.36 khash/s
[2013-05-10 09:58:39] accepted: 2/4 (50.00%), 86.34 khash/s (yay!!!)
[2013-05-10 09:58:40] accepted: 3/5 (60.00%), 86.34 khash/s (yay!!!)
[2013-05-10 09:58:43] LONGPOLL detected new block
[2013-05-10 09:58:43] thread 1: 143056 hashes, 9.54 khash/s
[2013-05-10 09:58:43] thread 3: 175437 hashes, 11.73 khash/s
[2013-05-10 09:58:43] thread 4: 61098 hashes, 13.12 khash/s
[2013-05-10 09:58:43] thread 0: 62878 hashes, 4.19 khash/s
[2013-05-10 09:58:43] thread 6: 19530 hashes, 1.31 khash/s
[2013-05-10 09:58:43] thread 2: 20946 hashes, 6.34 khash/s
[2013-05-10 09:58:43] thread 5: 167487 hashes, 11.17 khash/s
[2013-05-10 09:58:48] LONGPOLL detected new block
[2013-05-10 09:58:48] thread 4: 64145 hashes, 12.74 khash/s
[2013-05-10 09:58:43] thread 7: 14634 hashes, 3.14 khash/s
[2013-05-10 09:58:49] thread 0: 67879 hashes, 12.96 khash/s
[2013-05-10 09:58:49] thread 5: 248 hashes, 13.78 khash/s
[2013-05-10 09:58:49] thread 1: 68157 hashes, 12.78 khash/s
[2013-05-10 09:58:49] thread 3: 66818 hashes, 12.54 khash/s
[2013-05-10 09:58:49] thread 6: 8049 hashes, 3.38 khash/s
[2013-05-10 09:58:49] thread 2: 283 hashes, 13.48 khash/s
[2013-05-10 09:58:50] thread 4: 12376 hashes, 10.36 khash/s
[2013-05-10 09:58:55] thread 5: 77115 hashes, 12.25 khash/s
[2013-05-10 09:59:07] thread 0: 223817 hashes, 12.16 khash/s
[2013-05-10 09:59:11] thread 4: 69679 hashes, 3.39 khash/s
[2013-05-10 09:59:19] thread 1: 366488 hashes, 12.21 khash/s
[2013-05-10 09:59:21] HTTP request failed: Operation timed out after 30046 milli
seconds with 0 out of -1 bytes received
[2013-05-10 09:59:21] submit_upstream_work json_rpc_call failed
[2013-05-10 09:59:21] ...retry after 30 seconds
[2013-05-10 09:59:27] thread 7: 188370 hashes, 4.93 khash/s
[2013-05-10 09:59:42] thread 6: 199715 hashes, 3.78 khash/s
[2013-05-10 09:59:42] thread 3: 407517 hashes, 7.66 khash/s
[2013-05-10 09:59:47] thread 5: 661684 hashes, 12.65 khash/s
[2013-05-10 09:59:53] thread 2: 795058 hashes, 12.50 khash/s
[2013-05-10 09:59:54] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 10:00:06] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 10:00:06] submit_upstream_work json_rpc_call failed
[2013-05-10 10:00:06] ...retry after 30 seconds
[2013-05-10 10:00:52] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 10:00:52] submit_upstream_work json_rpc_call failed
[2013-05-10 10:00:52] ...retry after 30 seconds
[2013-05-10 10:01:37] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 10:01:37] submit_upstream_work json_rpc_call failed
[2013-05-10 10:01:37] ...retry after 30 seconds
[2013-05-10 10:02:23] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 10:02:23] submit_upstream_work json_rpc_call failed
[2013-05-10 10:02:23] ...retry after 30 seconds
[2013-05-10 10:03:08] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 10:03:08] submit_upstream_work json_rpc_call failed
[2013-05-10 10:03:08] ...retry after 30 seconds
[2013-05-10 10:03:54] HTTP request failed: The requested URL returned error: 502
 Bad Gateway
[2013-05-10 10:03:54] submit_upstream_work json_rpc_call failed
[2013-05-10 10:03:54] ...retry after 30 seconds

Etc.
It this because of ddos?

Please try the alternative server mineyac3.dontmine.me:8080 , 502 means cloudflare is blocking it

RIP my old pools... sometimes BTC isn't life ;(
Rannasha
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
May 10, 2013, 01:12:44 PM
 #128

Also getting a high reject-count (roughly 25% on both machines) coupled with periodic disconnect messages. Running on Ubuntu (both native & in a Win7 VM). Tried several of the servers.
Maniac
Hero Member
*****
Offline Offline

Activity: 868
Merit: 1000


View Profile
May 10, 2013, 01:13:36 PM
 #129

Its the same link as given by here

https://bitcointalk.org/index.php?topic=199517.msg2085725#msg2085725

but still be careful
also itll show up as the bitcoin miner on virustotal which I assume the original minerd also does but this may not nescessarily means its 100% safe/unsafe

run in vm/sandbox
also in linux itll give u way higher hashrate

Thank you!
This is win32 miner. Is exist 64-bit miner? Core i5 760 @ 2.80 Ghz - 46 kh/s is good speed?

Прокуратура запретила использовать криптовалюты, а также денежные суррогаты, заведомо печатаемые преступниками, т. е. рубли. Даёшь натуральное хозяйство!
paul21
Member
**
Offline Offline

Activity: 70
Merit: 10


View Profile
May 10, 2013, 01:14:52 PM
 #130

Also getting a high reject-count (roughly 25% on both machines) coupled with periodic disconnect messages. Running on Ubuntu (both native & in a Win7 VM). Tried several of the servers.

accepted: 8138/8319 (97.82%) for me on the local connection, so I think 502 is related to yac.dontmine.me and mineyac.dontmine.me , try mineyac3 it's not cloudflare

RIP my old pools... sometimes BTC isn't life ;(
Rannasha
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
May 10, 2013, 01:17:58 PM
 #131

Also getting a high reject-count (roughly 25% on both machines) coupled with periodic disconnect messages. Running on Ubuntu (both native & in a Win7 VM). Tried several of the servers.

accepted: 8138/8319 (97.82%) for me on the local connection, so I think 502 is related to yac.dontmine.me and mineyac.dontmine.me , try mineyac3 it's not cloudflare

ok, set one of my machines on mineyac3, lets see if it gets a better accept-rate.

The accept-rate was fine a while ago though, not sure when it started precisely.
Neverest
Jr. Member
*
Offline Offline

Activity: 56
Merit: 0



View Profile
May 10, 2013, 01:25:39 PM
 #132

Also getting a high reject-count (roughly 25% on both machines) coupled with periodic disconnect messages. Running on Ubuntu (both native & in a Win7 VM). Tried several of the servers.

accepted: 8138/8319 (97.82%) for me on the local connection, so I think 502 is related to yac.dontmine.me and mineyac.dontmine.me , try mineyac3 it's not cloudflare


Nope, similar results:
[2013-05-10 10:19:29] 8 miner threads started, using 'scrypt-jane' algorithm.
[2013-05-10 10:19:51] HTTP request failed: Failed connect to mineyac3.dontmine.m
e:8080; No error
[2013-05-10 10:19:51] json_rpc_call failed, retry after 30 seconds
[2013-05-10 10:20:34] Long-polling activated for http://mineyac3.dontmine.me:808
0/LP
[2013-05-10 10:20:34] thread 3: 4096 hashes, 12.96 khash/s
[2013-05-10 10:20:34] thread 1: 4096 hashes, 12.05 khash/s
[2013-05-10 10:20:34] thread 6: 4096 hashes, 10.29 khash/s
[2013-05-10 10:20:34] thread 0: 4096 hashes, 10.67 khash/s
[2013-05-10 10:20:34] thread 4: 4096 hashes, 12.84 khash/s
[2013-05-10 10:20:34] thread 7: 4096 hashes, 10.45 khash/s
[2013-05-10 10:20:34] thread 5: 4096 hashes, 9.06 khash/s
[2013-05-10 10:20:34] thread 2: 4096 hashes, 9.64 khash/s
[2013-05-10 10:20:39] thread 6: 64481 hashes, 13.02 khash/s
[2013-05-10 10:20:57] LONGPOLL detected new block
[2013-05-10 10:21:04] thread 7: 362667 hashes, 12.28 khash/s
[2013-05-10 10:21:04] thread 6: 20 hashes, 10.00 khash/s
[2013-05-10 10:21:04] thread 3: 194475 hashes, 6.55 khash/s
[2013-05-10 10:21:04] thread 4: 13945 hashes, 0.47 khash/s
[2013-05-10 10:21:04] accepted: 0/1 (0.00%), 60.63 khash/s (booooo)
[2013-05-10 10:21:06] thread 4: 28324 hashes, 12.47 khash/s
<snip>
[2013-05-10 10:22:02] thread 0: 32646 hashes, 8.28 khash/s
[2013-05-10 10:22:03] thread 7: 269427 hashes, 8.98 khash/s
[2013-05-10 10:22:05] LONGPOLL detected new block
[2013-05-10 10:22:09] thread 5: 73403 hashes, 3.95 khash/s
[2013-05-10 10:22:26] HTTP request failed: Failed connect to mineyac3.dontmine.m
e:8080; No error
[2013-05-10 10:22:26] submit_upstream_work json_rpc_call failed
[2013-05-10 10:22:26] ...retry after 30 seconds
[2013-05-10 10:22:27] thread 4: 40262 hashes, 1.40 khash/s
[2013-05-10 10:22:31] thread 6: 279067 hashes, 10.33 khash/s
[2013-05-10 10:22:34] thread 1: 719558 hashes, 12.22 khash/s
[2013-05-10 10:22:38] thread 3: 626870 hashes, 9.65 khash/s
[2013-05-10 10:22:48] thread 2: 785565 hashes, 10.57 khash/s
[2013-05-10 10:23:18] HTTP request failed: Failed connect to mineyac3.dontmine.m
e:8080; No error
[2013-05-10 10:23:18] submit_upstream_work json_rpc_call failed
[2013-05-10 10:23:18] ...retry after 30 seconds
[2013-05-10 10:24:09] HTTP request failed: Failed connect to mineyac3.dontmine.m
e:8080; No error
[2013-05-10 10:24:09] submit_upstream_work json_rpc_call failed
[2013-05-10 10:24:09] ...retry after 30 seconds

etc. Huh

20 years of crypto/Digicash experience. BTC: 1CHCSdHZj9Umcek2wKkwzRTB3rLkUb8yma
bengx
Full Member
***
Offline Offline

Activity: 202
Merit: 100


View Profile
May 10, 2013, 01:26:49 PM
 #133

Its the same link as given by here

https://bitcointalk.org/index.php?topic=199517.msg2085725#msg2085725

but still be careful
also itll show up as the bitcoin miner on virustotal which I assume the original minerd also does but this may not nescessarily means its 100% safe/unsafe

run in vm/sandbox
also in linux itll give u way higher hashrate

Thank you!
This is win32 miner. Is exist 64-bit miner? Core i5 760 @ 2.80 Ghz - 46 kh/s is good speed?

Yeah, I'm waiting out for the 64bit miner too. I actually get higher hash rates in a VM Ubuntu as opposed to running minerd on windows itself =\
Rannasha
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
May 10, 2013, 01:29:16 PM
 #134

Its the same link as given by here

https://bitcointalk.org/index.php?topic=199517.msg2085725#msg2085725

but still be careful
also itll show up as the bitcoin miner on virustotal which I assume the original minerd also does but this may not nescessarily means its 100% safe/unsafe

run in vm/sandbox
also in linux itll give u way higher hashrate

Thank you!
This is win32 miner. Is exist 64-bit miner? Core i5 760 @ 2.80 Ghz - 46 kh/s is good speed?

It's not. You should run Ubuntu in a VM if you can (or ideally, without VM and directly), to get better speeds. I get double that hashrate on a laptop i7 of the same generation.
paul21
Member
**
Offline Offline

Activity: 70
Merit: 10


View Profile
May 10, 2013, 01:34:13 PM
 #135

I should have fixed the dropped connections. I hadn't whitelisted my forwarders, oops!

RIP my old pools... sometimes BTC isn't life ;(
JahPowerBit
Sr. Member
****
Offline Offline

Activity: 300
Merit: 250


Counterparty Developer


View Profile
May 10, 2013, 01:40:23 PM
 #136

paul21, thank you for this good job.
You think you will share in github your code or keep only for you ?
we need more and more pool! thks.

.
   █████▄▄▄▄
   ████████████▄▄▄            ▀██████
   ███ ▀▀▀▀█████████▄          ▀█████
   ███         ▀▀▀█████▄         ▀███
   ███              ▀▀████▄▄███    ▀▀
   ███                ▀███████▀
   ███                    █████
   ███     ███▄         ▄███████
   ▐██▌     ▀███▄     ▄███▀  ███
   ▐███       ▀███▄▄ ███▀     ███
    ███▌        ▀████        ▐██▌
     ███         ████         ███
      ███      ▄█████▄       ▐██
       ███   ▄████▀ ▀███▄     ▐██
        ███▄████▀     ▀███▄   ███
         █████▀         ▀███▄████
          ██▀             ▀█████▌
                            ▀███▌
  ██████                      ▀▀
  ▀▀▀███
     ███
█         █   ███
 █        ███  ███  █
███       ███   █  ███
███   █   ███   █  ███
███  ███   █       ███
███  ███   █       ███
 █   ███            █
 █    █             █
█         █   ███
 █        ███  ███  █
███       ███   █  ███
███   █   ███   █  ███
███  ███   █       ███
███  ███   █       ███
 █   ███            █
 █    █             █
             JOIN US             
TELEGRAM TWITTER FACEBOOK
LINKEDIN WHITEPAPER
paul21
Member
**
Offline Offline

Activity: 70
Merit: 10


View Profile
May 10, 2013, 01:41:24 PM
 #137

paul21, thank you for this good job.
You think you will share in github your code or keep only for you ?
we need more and more pool! thks.

I'll share it once I get home from work, it's actually a really simple change.


RIP my old pools... sometimes BTC isn't life ;(
Neverest
Jr. Member
*
Offline Offline

Activity: 56
Merit: 0



View Profile
May 10, 2013, 01:42:36 PM
 #138

I should have fixed the dropped connections. I hadn't whitelisted my forwarders, oops!

Yep, it's better now, thanks.
I got it running on Win7 64 and on Ubuntu (in VMware). Both take 50% cpu and connections are good on both.
Interestingly the virtual Ubuntu has double hashing speed and much higher amount of accepted shares (10-20 times more), not sure why.

20 years of crypto/Digicash experience. BTC: 1CHCSdHZj9Umcek2wKkwzRTB3rLkUb8yma
JahPowerBit
Sr. Member
****
Offline Offline

Activity: 300
Merit: 250


Counterparty Developer


View Profile
May 10, 2013, 01:43:13 PM
 #139

paul21, thank you for this good job.
You think you will share in github your code or keep only for you ?
we need more and more pool! thks.

I'll share it once I get home from work, it's actually a really simple change.


Thank you very much. Maybe simple change but very important for all of us ;-) thank you again.

.
   █████▄▄▄▄
   ████████████▄▄▄            ▀██████
   ███ ▀▀▀▀█████████▄          ▀█████
   ███         ▀▀▀█████▄         ▀███
   ███              ▀▀████▄▄███    ▀▀
   ███                ▀███████▀
   ███                    █████
   ███     ███▄         ▄███████
   ▐██▌     ▀███▄     ▄███▀  ███
   ▐███       ▀███▄▄ ███▀     ███
    ███▌        ▀████        ▐██▌
     ███         ████         ███
      ███      ▄█████▄       ▐██
       ███   ▄████▀ ▀███▄     ▐██
        ███▄████▀     ▀███▄   ███
         █████▀         ▀███▄████
          ██▀             ▀█████▌
                            ▀███▌
  ██████                      ▀▀
  ▀▀▀███
     ███
█         █   ███
 █        ███  ███  █
███       ███   █  ███
███   █   ███   █  ███
███  ███   █       ███
███  ███   █       ███
 █   ███            █
 █    █             █
█         █   ███
 █        ███  ███  █
███       ███   █  ███
███   █   ███   █  ███
███  ███   █       ███
███  ███   █       ███
 █   ███            █
 █    █             █
             JOIN US             
TELEGRAM TWITTER FACEBOOK
LINKEDIN WHITEPAPER
paul21
Member
**
Offline Offline

Activity: 70
Merit: 10


View Profile
May 10, 2013, 01:43:52 PM
 #140

Share difficulty was bumped to reduce load on the server.

RIP my old pools... sometimes BTC isn't life ;(
Pages: « 1 2 3 4 5 6 [7] 8 9 10 11 »  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!