61
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool (up to 501% faster)
« on: November 15, 2013, 04:55:35 am »
Nooooooooo
Beeeeeerrrrrrr....
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.
Nooooooooo
Beeeeeerrrrrrr....
62
BitShares PTS / Re: Coyote Pool 2.0 - One Day Rounds Proportional Payout
« on: November 15, 2013, 01:15:12 am »
Just testing this miner out, its been running smooth so far.
I am getting 30hpm on linux 8core with 8 or 16 threads.
I am getting 70hpm in win76core with 6 or 12 threads.
It seems to put out more shares at 1 thread per core. Are these hpm's about right or do I need to slap it around a bit?
Also, How can I see how many total shares Ive submitted so far, is there a block\user display like beeerpools we can look at?
Thanks
I am getting 30hpm on linux 8core with 8 or 16 threads.
I am getting 70hpm in win76core with 6 or 12 threads.
It seems to put out more shares at 1 thread per core. Are these hpm's about right or do I need to slap it around a bit?
Also, How can I see how many total shares Ive submitted so far, is there a block\user display like beeerpools we can look at?
Thanks
63
Marketplace / Re: [WTS] 100 PTS @ 0.0073
« on: November 15, 2013, 12:59:54 am »
I will buy 100 PTS @ 0.0073.
Want to use favdesu for escrow and split it?
Want to use favdesu for escrow and split it?
64
BitShares PTS / Re: [GUIDE] Mining on Amazon EC2 using Spot instances
« on: November 14, 2013, 10:38:40 pm »
Yeah, they are upping the prices and killing my sessions now.
It was fun while it lasted!
It was fun while it lasted!
65
General Discussion / Re: Pre-order a Keyhotee ID
« on: November 14, 2013, 10:00:20 pm »
I do not like the idea of a public list. People with excessive funds could just buy up all the cool names on the list.
I am certain that a couple I would register would cause a bidding war, so I would not add them until the last minute.
A web page with a search field that tells you if the name is taken and takes any bid would make this a little more fair and private.
I am certain that a couple I would register would cause a bidding war, so I would not add them until the last minute.
A web page with a search field that tells you if the name is taken and takes any bid would make this a little more fair and private.
66
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool (incl. RJ-Fix&64Bit&OSX)
« on: November 12, 2013, 06:49:31 am »
Confirmations seem to have stopped at block 12351.
19 new blocks have been found since that block was confirmed and paid out, but no confirmations have happened since then. (at least on my payout screen)
Any idea whats up?
19 new blocks have been found since that block was confirmed and paid out, but no confirmations have happened since then. (at least on my payout screen)
Any idea whats up?
67
General Discussion / Re: TESTERS WANTED - Follow This thread to become Alpha Testers!
« on: November 12, 2013, 06:41:57 am »
following...
68
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool! (RJ-Fix & 64Bit)
« on: November 10, 2013, 07:25:27 pm »
@gnarl:
backend is already updated.
- xolokram
awesome, v.04 is rockin too, thx
69
General Discussion / Re: CHAIN FORK COMING....
« on: November 10, 2013, 07:16:18 pm »No release notes and no version number change? cmon...
I noticed Getmininginfo does not list hashespermin anymore, it now shows collisionspermin instead.
What else has changed?
Yep it was a rushed job... we are in the process of putting together a rollout checklist and testing procedures so we don't have to fly by the seat of our pants in the future. With blocks flying every 20 seconds we had to act fast.
How can we as a community help? Do you have a list of people to test new builds? You have a lot of support here, don't be afraid to ask in these situations.
70
General Discussion / Re: CHAIN FORK COMING....
« on: November 10, 2013, 06:30:36 pm »
No release notes and no version number change? cmon...
I noticed Getmininginfo does not list hashespermin anymore, it now shows collisionspermin instead.
What else has changed?
I noticed Getmininginfo does not list hashespermin anymore, it now shows collisionspermin instead.
What else has changed?
71
BitShares PTS / Re: [ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool! (RJ-Fix & 64Bit)
« on: November 10, 2013, 06:22:41 pm »
xolo - I like your pool, its been working good since you released it.
Questions about the fork
When will you switch over? Do miners need to do anything like restart all clients?
What do you think of the 2 hour notice to discuss the fork?
Questions about the fork
When will you switch over? Do miners need to do anything like restart all clients?
What do you think of the 2 hour notice to discuss the fork?
72
BitShares PTS / Solo mining hang
« on: November 09, 2013, 01:56:51 am »
I have noticed a problem with the Protoshares-qt miner when solomining. The problem occurs after it finds a block and determines that it will reject it due to being found within a few seconds of another. The mining process seems to hang up and stop connecting to the network after getting a 'not accepted' block. The protoshares-qt program keeps using cpu\memory, but does not connect to the network anymore, and just shows repeated hashtarget\testhash log entries.
I have seen this problem a couple times now on 2 different machines, and have saved the log if devs need it.
Here are the details:
This occurred each time while Mining 3 Processes, and setgenerate true 3, no other settings changes.
A block is found and placed in the Immature category.
Listtransactions shows
account" : "",
"address" : "PY4pRRpyhDn1Uf4VpzrwZgNantbpTZnQgZ",
"category" : "immature",
"amount" : 42.86875000,
"confirmations" : 1,
"generated" : true,
"blockhash" : "00028edad5886a66fecc7f4ecda60e954c5320fcdf6aba54522521f7bfe9127e",
"blockindex" : 0,
"blocktime" : 1383947664,
"txid" : "e30f8e6a0ecc8c7e4c0c83fdccedd033b44a080a806cf7d0fc84060e3995fec1",
"time" : 1383947664,
"timereceived" : 1383947686
The confirmations never update past 1, no matter how many hours you wait.
The protoshares-qt miner appears to be mining\doing work (processor and memory use is shown in windows task manager), but the log shows nothing but pages of Hash Target and testhashes.
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash 9bae1c286298d10d6e6d4231b43c110fddbe317a3a7f87b8b2457df1d1aa0800
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash 0396d9bb17f49f49af80b0e4ee32c2a319579c507b1dd08556eb92dd0b4d6580
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash 32582d39b79f2d779d516b6c1eff9708e5817bf80972ada2f39d0080cb481c44
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash d5b2960fd161bf13874e8c4e112be5967a8b9603e63c858c6c58241d35253c46
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
hashmeter 0 khash/s
testHash 6c1e69de4af3dd2361d31e80544e301e1bae931f918b32baa46a97a41923dd34
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash 36b316a4182cc9ff23d83bcdc21ddf44995577d10222684573d4f8bbf35b25f3
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash 3d01df93e6d5bbffc45fd1f559ff5c39d53ea74a6dfebde7744ade51cc0693d2
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
There are no accepted or rejected blocks after this happens. You must restart protoshares-qt to mine successfully again.
After restarting protoshares-qt the transaction will be removed from the immature listing and placed in a transaction. Details now show
Status 0/unconfirmed
Date: 11/8/2013 13:54
Source: Generated
Credit: (not accepted)
Net amount: 0.00 PTS
The 1 confirmation is lost, and the credit is not accepted.
The transaction details say:
When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.
This is fine, except that the miner log looks like its not actually mining correctly anymore, just chewing on processor\memory.
Has anyone else seen the miner hang like this?
I have seen this problem a couple times now on 2 different machines, and have saved the log if devs need it.
Here are the details:
This occurred each time while Mining 3 Processes, and setgenerate true 3, no other settings changes.
A block is found and placed in the Immature category.
Listtransactions shows
account" : "",
"address" : "PY4pRRpyhDn1Uf4VpzrwZgNantbpTZnQgZ",
"category" : "immature",
"amount" : 42.86875000,
"confirmations" : 1,
"generated" : true,
"blockhash" : "00028edad5886a66fecc7f4ecda60e954c5320fcdf6aba54522521f7bfe9127e",
"blockindex" : 0,
"blocktime" : 1383947664,
"txid" : "e30f8e6a0ecc8c7e4c0c83fdccedd033b44a080a806cf7d0fc84060e3995fec1",
"time" : 1383947664,
"timereceived" : 1383947686
The confirmations never update past 1, no matter how many hours you wait.
The protoshares-qt miner appears to be mining\doing work (processor and memory use is shown in windows task manager), but the log shows nothing but pages of Hash Target and testhashes.
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash 9bae1c286298d10d6e6d4231b43c110fddbe317a3a7f87b8b2457df1d1aa0800
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash 0396d9bb17f49f49af80b0e4ee32c2a319579c507b1dd08556eb92dd0b4d6580
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash 32582d39b79f2d779d516b6c1eff9708e5817bf80972ada2f39d0080cb481c44
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash d5b2960fd161bf13874e8c4e112be5967a8b9603e63c858c6c58241d35253c46
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
hashmeter 0 khash/s
testHash 6c1e69de4af3dd2361d31e80544e301e1bae931f918b32baa46a97a41923dd34
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash 36b316a4182cc9ff23d83bcdc21ddf44995577d10222684573d4f8bbf35b25f3
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash 3d01df93e6d5bbffc45fd1f559ff5c39d53ea74a6dfebde7744ade51cc0693d2
Hash Target 0003ffc000000000000000000000000000000000000000000000000000000000
testHash ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
There are no accepted or rejected blocks after this happens. You must restart protoshares-qt to mine successfully again.
After restarting protoshares-qt the transaction will be removed from the immature listing and placed in a transaction. Details now show
Status 0/unconfirmed
Date: 11/8/2013 13:54
Source: Generated
Credit: (not accepted)
Net amount: 0.00 PTS
The 1 confirmation is lost, and the credit is not accepted.
The transaction details say:
When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.
This is fine, except that the miner log looks like its not actually mining correctly anymore, just chewing on processor\memory.
Has anyone else seen the miner hang like this?
