Topic: [0Th]Ozcoin Pooled Mining |DGM 1%|Stratum+VarDiff port 80|NEW CN mining| - page 123. (Read 398185 times)

I get: Welcome to Ozcoin's DGM Pool.

>nslookup ozco.in

Non-authoritative answer:
Name:    ozco.in
Addresses:  2400:cb00:2048:1::c71b:87c2
          2400:cb00:2048:1::8d65:7cc3
          141.101.124.195
          199.27.135.194

>nslookup 199.27.135.194
Name:    cf-199-27-135-194.cloudflare.com
Address:  199.27.135.194

It seems like the 141 cloudflare IP is not configured correctly. Try putting the 199 IP in your hosts file for ozco.in. You also may be accessing with IPv6 AAAA but something along the line (like your ISP) doesn't support it.

I get the same error for both
http://ozco.in/
https://ozco.in/

Sam

Use the non-SSL site (which is working for at least two days now ;-).

Is the website supposed to be up yet?  I'm still getting "Website Offline, No Cached Version Available"
Sam

Notable to mention since it hasn't been yet: consider one of the files that could have been copied to be the password file, a la mtgox hack. I would suggest all users regard their credentials used on the pool as out in the open to hackers, and change the pool account password and workers or make a new account. Additionally make sure that any other assets using the same password, username, email, etc, get burned or at least the password changed. Just a note, I have little worry, because my unique username and password for the pool are long with random generated characters like UA12mj(\)#yB#Cl0Z)Uz{&5pz_, and the email a non-reversible disposable email address, do this everywhere and you are pretty safe.

Pool's going strong, last block found in 10 hours. 2356 Accepted/6 Rejected with no hiccups or waiting for work (yes, you, btcg).

Update
When the pool wallet was emptied a lot of users wallet payout addresses displayed an "invalid" message after an unsuccesful payout.
All miners please check your wallet address and payout thresholds if you are not recieving payments. Please note this is how the software was configured and was not anything malicious.
We have changed the code so this will not occur again
Whilst we monitor our new setup payouts are run manually ~ every 8hours,we expect to return to normal auto payouts every 10mins within the next 48hours:)

In light of recent events I would strongly encourage all miners to take responsibilty for their own BTC and not let funds accumulate in any pool wallet. Whilst our best efforts are taken to ensure miners and pool funds are safe we do not have the sort of money Sony or Banks have to spend on security - and they still get hacked... lets be sensible about this

Also we have setup a seperate "payout" wallet that will contain minimum funds, if you do accumulate funds in the pool wallet there may be a delay if you try to withdraw a large sum.
We were extremely lucky last time and whilst every effort is being undertaken to secure the site and funds, relying on luck in a worst case scenario is a fail option

Good things happen to good people.

g'nite mate!

finally
reinstalled and setup 3 servers
currently 2 mining nodes in USA and EU
AU server is running the db and www
plans for au mining underway

We took a bit longer to setup than hoped, the good news is none of the bitcoinds used for mining have any coins touch them anymore. All generated coins will go to a wallet not on or associated with our servers.

kudos to p2k and Littleduke, ecoinpool is proving to be superior pool software. p2k's efforts to help us get up and running again have been above and beyond the call. LittleDuke got back from a weekend away saw we were desperate, rolled up his sleeves and powered through. Thanks guys

The main focus has been on getting the pool up,
now comes the post mortem

we had 7 blocks of btc removed from the wallet as soon as they matured = 350BTC
about 150BTC were withdrawn brefore the blocks started being taken, so a total of around 500BTC including 50BTC of donations 

The thing that blew me away: I said on irc that I would mine on eu and see if i could jag a block "solo" one guy said he'd point a rig there too, I told him no db so no share counts or payouts, just "charity" shares, someone else said theyd point a card as well, somehow the word spread, we found 9 yes 9!!! blocks, a total of 450BTC
Just wow!
If we disallow the donations the pool is actually even 

I'm going to watch for a while then collapse into sleep, thank you all the wonderful people that supported Ozcoin through this trying time

Best wishes
Graeme

a quick "where we stand"

Pending Payout (unconf.):    247.31891786 BTC
Pending Payout (conf.):    215.51497114 BTC

was the last stats displayed, there were some blocks solved after this that need to be calculated in.

We currently have enough funds to cover confirmed payouts and over half of the unconfirmed

On past performance of Ozcoin on DGM and with continuing support from miners I believe we can continue to operate and "trade out of our difficulties" within 1 month.

I am hoping not, but we may have to "delay" some payments as wallet is refilled.

I will update with more info as I am able to.

Graeme

pretty impressive graet, the donation pool has a higher hash rate then the old ozcoin pool before dgm method
Rate:  31.8GH/s - Stales: 0.09 %
In times of adversity we find who our true friends are, thank you friends

* Graet wipes a tear from corner of eye

Taking longer to get back online than planned - better to be sure than rush at this stage we think 

A couple of ppl have asked for an adress to send some help to 1Gzcbs8dDYzf16qFWKHc5kWKuH8nji3pVt

Dunno what to say, for every word of anger I spoke before I now have one of thanks to the wonderful people -maybe the silent majority- from this community

Thanks
Graeme

Sending my hashes your way Graet

Mate - you've got my 8 Ghash running all the way through this bullshit and I'll continue to stay on your servers.

Was wondering why I couldn't get into the screens... but rest assured, all my rigs are still supporting your pool.

Hang in there old chap.

cheeers, catfish

No I use my own php on my own bitcoind and 165519 is not gonna be changing away from ozco.in without the biggest chain of orphans yet to occur (and then you'd lose those 3 also )

At this moment blockchaininfo's "orphan block" page shows incorrect branch as the winning one. It was changed at least once, but still wrong.

165525-165526-165527 are Deepbit's blocks.

So looking at the actual block chain in relation to the comments
165518: slush
165519: ozco.in
165520: Eligius
165521: BTC Guild
165522: ?
165523: slush
165524: BTC Guild
165525: ?
165526: ?
165527: ?
165528: ?
165529: ?
165530: ?
165531: ?
165532: Eligius

So I'm not sure what Tycho (165519) or deepceleron (3 deepbit blocks) are talking about.
Maybe deepceleron means some of the '?' blocks 6 blocks after the one being discussed

I already fixed it.

Looks like btcguild took the (spanish pool)->eligius block instead of the ozco->simplecoin block even though both were older. Then deepbit buries it in three blocks in a minute. Conspiracy!

Blockchaininfo somehow shows it on the WRONG side...

thanks deepceleron
we did find a block AND managed to be on the correct side of a 2 block fork!! some luck

165519

we did setup a script and managed to recover 1 block b4 it was snatched, but most were gone before we got the script up.