BTC per-block estimates should be accurate now.
|
|
|
As I've said several times now, I will be paying all the shares in the DB submitted since Oct 8 until we reach a total payout of 30 BTC. After that, the BTC port will switch to 24 hour PPLNS to match p2pool.
|
|
|
Great news about hooking in to p2pool. I've been watching this pool and have done a little mining. I love the concept, but the BTC variability has been holding me back.
One question, how are existing BTC share submittals going to be handled? Will they still be counted since a BTC block has not yet been found?
I'm going to be paying out all the shares in the DB until we reach 30BTC of payments. That should take about two weeks at the current hashrate. After that I will likely change to a 24 hour PPLNS on the BTC port as that's how p2pool pays out. Doesn't p2pool keep 3 days worth of shares currently? The wiki says: Each share contains a generation transaction that pays to the previous n shares, where n is the number of shares whose total work is equal to 3 times the average work required to solve a block, or 8640 (= 24 hours of shares), whichever is smaller. Payouts are weighted based on the amount of work each share took to solve, which is proportional to the p2pool difficulty at that time.
It's a bit ambiguous, but I believe it means the PPLNS is 24 hours, or 3x the average work, whichever is smaller.
|
|
|
Don't they reset the testnet and kill all the coins on a semi-regular basis?
|
|
|
Back to scrypt for a moment, what do people think of TagCoin?
put all these up for mining, they give us interest on all deposits including btc interest https://mcxnow.comO and thanks for fixing NVC for me I'm pretty sure we already mine all the mcxnow scrypt coins. DVC merged mining is coming soon.
|
|
|
Twelve days of BTC mining after a £1200 ASIC investment and (almost) now the proud owner of 0.0006 BTC (+0.1 BTC from the sha pool). Booking my Caribbean holiday now :-) I'll pay for everybody else on Multipool to come along too ;-)
Just one question as I can't discern the answer from previous posts. Is the BTC 'per block estimate' figure meaningless now?
Thanks.
K
Pretty much, however since p2pool has a json API I'll be able to pull our estimate out of there, and fix the BTC estimate using that.. I just haven't had time to do it yet.
|
|
|
Back to scrypt for a moment, what do people think of TagCoin?
|
|
|
Great news about hooking in to p2pool. I've been watching this pool and have done a little mining. I love the concept, but the BTC variability has been holding me back.
One question, how are existing BTC share submittals going to be handled? Will they still be counted since a BTC block has not yet been found?
I'm going to be paying out all the shares in the DB until we reach 30BTC of payments. That should take about two weeks at the current hashrate. After that I will likely change to a 24 hour PPLNS on the BTC port as that's how p2pool pays out.
|
|
|
well thinking it staying around 67 diff now, still high also my reported hash rate is 2 gh/s guess its that rush of shares coming in ever 5 mins weren't you going to take btc off the mp roster and let people choose to mine btc? anyways glade we finally solved a block. also my NVC payment is still in limbo. (requested) .. just put back in my balance please along with the .1 that got taken out thanks Nothing gets taken out until the transaction is processed. I've canceled your withdrawal.
|
|
|
ah back to mp and getting 74 diff at time of post mining btc... with only 1gh/s 2nd thought its working even at 64 diff i can see my hashes and submitting shares think we are good 3rd thought its taking wayyyy to long to submit shares... ~ 5 mins per share = not good @ 47 diff @ 1 gh/s It shouldn't *really* matter all that much.. But I'll work on getting custom difficulty implemented.
|
|
|
I'm at 43 now on the BFL little single.. Pretty close to what I had (32)
|
|
|
Uh oh...I'm at Diff 301/147 now It's set for Share Diff 4 for this worker. p2pool currently does not respect custom difficulty settings as implemented by Multipool.
|
|
|
Aww...and here I was having fun making "Bruce Lee noises" as I Karate chopped Share Diff 300+ blocks on my wee lil Erupters Yep my 3 usb miners are @ 89 diff atm lol give it them sure it will hit back up to 1k diff .. again Are they all using the same worker?
|
|
|
Share difficulties should be a bit more sane now.
|
|
|
Payouts were just calculated for the first block.. Let me know if anything doesn't look right. I'm going to pay all the shares in the DB until we reach 30 BTC of rewards.
So does this mean we all are going to get paid the shares we have submitted for the past month, or just the 1's scene p2p start today? Almost there , keep up the good work.. All the shares since October 8 when the BTC port went live.
|
|
|
Payouts were just calculated for the first block.. Let me know if anything doesn't look right. I'm going to pay all the shares in the DB until we reach 30 BTC of rewards.
|
|
|
Well I can confirm that adding "--request-diff 1" sets difficulty for 1 for a few accepts, but then cranks up to the stratosphere within 15-20 secs...
I did get an accept at difficulty 271 -- lol this is a lucky little erupter!
It always starts at 1 no matter what.
|
|
|
Which port is your pool zero??? Read the last two pages and the home page. flound has patched us into p2pool BTC!!! Keep yer pants on, payouts gonna git regular pool1.us.multipool.us:8888 It started hashing again, and is now back to "requested work update" -- did an "increasing queue minimum to 3" a bit ago as well. Do I need to reconfigure anything in my command line? I'm trying to force it to lower the share difficulty.. It's giving my BFL little single a diff of ~430 which is way too high. Yikes It's giving my Block Eruptors diff 639!!! Diff = 1 would be best. My BFL Singles are getting 482 to 639 and it changes frequently, which is fine. Are you using the same worker name for all those?
|
|
|
First block... We're rich!! $ bitcoind listtransactions [ { "account" : "", "address" : "146197ntzrBT41DDQRrB2STBb19dw7ct2F", "category" : "immature", "amount" : 0.03131972, "confirmations" : 1, "generated" : true, "blockhash" : "00000000000000011a839886f00a638ec3b19da427ee512f0021c1e7b511c67a", "blockindex" : 0, "blocktime" : 1383697545, "txid" : "a302adbe437dbc2ce84d4e9e2c53cdc952c0101b3e88745a9b1a602b2d6cc005", "time" : 1383697545, "timereceived" : 1383697563 } ]
|
|
|
|