Congrats to '255e8151' who hit 50,000 shares and has been paid a 4BTC bonus. The next 3 getting close to 50k have share values of 45400, 20,800, and 19,800.

I've made the necessary pool changes to make the DGM share count accurate and this will be rolled out after the next block or so. You'll then see the number of shares for the DGM payments and the PPS payments separately on the page and the API.

Yes, good idea. I'll add that.

4 BTC then 3 BTC, 2 BTC, 1 BTC, then it's done.

Last DGM related pool change for a bit. I've added a "last 5 payments" to the user stats page. This shows the actual amount of BTC paid for the last few blocks. I'll clean up the look of this later, I just wanted to get something quick out there.

Can you PM me your ip address? I banned a range from someone attempting a mass SQL injection attact and you may be caught up in it.

Edit: Actually if you can't reach stratum2.bitparking.com then it's not that. What error are you getting?

Congrats to '6a407671' who hit 50,000 shares and has been paid a 5BTC bonus. The next 4 getting close to 50k have share values of 32000, 14,600, 14,400 and , 7800.

I put some DGM stats here. Note that the 'score' shown in the estimates is an estimate and could be off by a few. The score in the payouts should be accurate however.

What this doesn't show is the effect of the PPS miners. All the PPS miners effectively contribute to DGM so the pool has an internal PPS user that accrues DGM value. If there's interest I can show that too. I'm not quite sure the best way to display or word it though.

I've added a temporary stat to the user page that shows the total number of DGM shares mined so you can see how close to the 50,000 you are.

Thanks to the following users who get 1 btc for being the top 5 share submitters on the dgm stratum node (Usernames are the first 8 characters of the sha256 hash of their username):

• 6a407671: 6188
• f4b05c10: 2968
• 57a22ab2: 1416
• a5d78fff: 1360
• 906b1bc4: 623

1 BTC has been sent to the bitcoin address associated with these users accounts.

I'm opening the DGM server for wider testing. To mine on the DGM server with stratum use stratum+tcp://mmpool.bitparking.com:4333. Note the '4333' at the end instead of '3333' which is the PPS server. The details of the DGM server are:

• 1.5% fee
• f=-0.23125
• c=0.2
• o=0.8

Details about DGM (and what 'c' and 'o' mean) are available at the Double Geometric Method forum post. Unlike PPS, where constant payments are made for each share, your DGM balance works like a capacitor. When you first start earning the amount is lower while the capacitor charges. When fully charged the earnings are more regular. When you stop mining the capacitor discharges and you still get paid for a period afterwards. So don't panic if earnings seem lower at the beginning. Even if you stop mining on DGM you'll continue to accrue DGM amounts where you'll catch up. Stastically you should earn more on DGM due to the lower fee.

Due to the way DGM operates payments are made when a block is found. You will see a "DGM Estimated Round Payout (BTC)" in your user statistics page. This is the estimated amount of BTC you are likely to earn when a block is found. You'll notice this will have a value in future blocks even when you stop mining due to the capacitor approach described before. You can switch between PPS and DGM any time.

Feedback on DGM, the stats shown, and the parameter settings the pool is using, are welcomed.

Note that this is experimental and if there are issues let me know so I can track them down. I reserve the right to shut the DGM server down should I find a major problem so you should set up a backup server. If I shut DGM down I'll redirect to a PPS server.

First user that hits 50,000 DGM shares and emails/bitmessages/PM's me to confirm gets a 5 BTC bonus sent to their registered BTC address for helping test. Second, third, fourth and fifth get 4, 3, 2 and 1 BTC respectively but remember you need to email/bitmessage/PM me so I can confirm to be eligible! If I have to close DGM early due to issues I'll apportion based on nearest hash rates to 50,000 at the time.

Edit: I'll also throw in 1 BTC each to the top 5 highest score submissions on the DGM server as at Saturday, 27 April 2013 00:00:00, GMT. That's two hours from now. This should give the lower hash rate, but early testers, a chance for a reward.

Edit 2: 40 minutes to go until the 1 BTC awards mentioned in the edit. Currently the top five have 2720, 2080, 864, 546 and 258 shares. Thanks for testing!

I have a devcoin seed node running at . This connects to my mining pool node which is mining Devcoin at about 4 Thash/s so gets notification of new blocks fairly quickly. My devcoin address is 1KXrxx7skEeTapMZiV67MHo699hS6BrcEZ.

I fired up my coiledcoin client a few weeks ago to see if it was still alive but noticed there were multiple chains. One client I connected with had a block count ahead of the blockchain explorer, with different hashes for the blocks with the same numbers as the explorer, but another client I connected with on a different machine matched the block explorer. Neither chain reorg'd when connected to each other.

New stats added to the user page and the userstats JSON API:

• Shares for round. This is the number of equivalent difficulty 1 shares submitted since the last block found
• PPS for round. This is the number of BTC earned from the PPS system since the last block found. If you haven't done any DGM mining (when it's enabled) this should be the 'shares for round' multipled by the current BTC rate - assuming difficulty hasn't changed mid round.
• DGM Estimated Round Payout. This is the estimated amount of BTC that would be earned when the next block is found for the shares submitted to the DGM system.

The main page also shows the hash rate going towards the DGM reward system (not currently enabled, still in testing).

Wallets refilled, withdrawals are now working.

Pool is back up. I've defragmented the wallets and they're currently empty. I'll be sending the funds from the old wallets shortly then withdrwals can resume.

Pool down for 10 minutes for a coin daemon upgrade.

Hello IP address 46.165.208.105, nice try running a script to try and SQL inject user logins. but please don't test the security of the pool without asking me, thanks.

There's a miner on the main stratum server that is sending invalid hashes and getting H-not-zero responses as a result. It looks like they haven't noticed. The hashes look to be scrypt based. If You are user "Lxxxxxe" ('x' are other characters, blanked out to prevent revealing the name) then you might want to check your configuration. It looks like you have an asic and it's being wasted.

There are two miners on the stratum2 server that appear to be asics but are forcing a difficulty of 1. This is causing quite a large bandwidth usage on the server. I've forced that stratum server to send a minimum of difficulty 8 shares as a result. If you're on that server please check your password to see if you're configured for difficulty one shares.

Thanks, I appreciate the kind words. At the moment I'm planning to add DGM to the pool and offer both PPS and DGM. The choice of which reward scheme you want would be based on the server you mine on. I will probably have a higher fee for PPS and a lower fee for DGM. I'm running DGM at the moment in testing and it seems to be working fine.

Thanks, I assume the 'r' used in that calculation should be calculated using a 'p' adjusted for the difficulty of the share that solved the block too?