 Show Posts
|
|
Pages: « 1 [2] 3 »
|
|
There's still hashing activity.
|
|
|
|
|
Spots stalled.
Where do we report issues like that now?
|
|
|
|
|
blockchain has forked or something happened (100% rejects)
|
|
|
|
I'm solomining HBN just fine, no idea what's wrong with that one.
The newest client is 1.2.2, they're running an outdated client on the pool.
Perhaps not, there was an issue with HBN tonight. Please make sure you match coinwarz before you solo. I am putting the block chain into a download for ease of re downloading. It sorta matches, I'm mining like 80% of all blocks with 15MH/s so it doesn't suprise me i'm ahead of coinwarz. Edit: yeah, coinwarz is following me by a few minutes. |
|
|
|
|
I'm solomining HBN just fine, no idea what's wrong with that one.
The newest client is 1.2.2, they're running an outdated client on the pool.
|
|
|
|
|
I think something's wrong with the HBN pool
|
|
|
|
17:34:25 ? getinfo 17:34:25 ? { "version" : 60300, "protocolversion" : 60001, "walletversion" : 60000, "balance" : 1303.30000000, "blocks" : 385801, "connections" : 8, "proxy" : "", "difficulty" : 0.42616352, "testnet" : false, "keypoololdest" : 1377682571, "keypoolsize" : 101, "paytxfee" : 0.00000000, "mininput" : 0.00010000, "errors" : "Mandatory upgrade to Litecoin 0.8.5.1+. https://litecoin.org/upgrade" } Dumped from my wallet. |
|
|
|
|
Alphacoin is stuck, about 15000 blocks behind the chain.
|
|
|
|
|
It looks like the diffs are off on a few of the coins.
Lucky, Alpha, Cosmos, and Craft are not right (there might be more)
BBQ is wrong as well, they've stalled and are on the wrong block.
|
|
|
|
1 Million premined coins  Can we get the address for those coins so we can make sure they don't go to an exchange? |
|
|
|
|
use one of the pools as a node?
|
|
|
|
|
What address is that 1 million coin premine at so we can watch it and make sure it doesn't go to an exchange?
|
|
|
|
|
here are some IPs I pulled from netstat
178.73.198.5:4818
108.254.141.122:4537
24.10.97.6:4534
173.246.103.92:4533
|
|
|
|
Someone attempted a 51% (while the pools were down, dunno if they took them down). I blocked it with my mining farm. (This comment is actually serious, surprisingly) Proof: https://i.imgur.com/8EeRFJi.pngEvery time that bad blockchain appeared at the bottom, I restored for a backup blockchain I had made when I noticed the attack. Eventually it stopped happening. (maybe he succeeded and I 51%ed back to the original blockchain?) |
|
|
|
The FTC attack was probably conducted by one of the big LTC pools, as that's the only way to suddenly redirect hundreds of MH/s of scrypt miners.
I doubt it, you could probably detect it by looking at which LTC pool had bad luck that was outside of several standard deviations during the attack. |
|
|
|
|
Trying to 51% LTC would:
1) cause all auto-miners to autoswitch onto LTC (same as FTC).
2) cause anyone with LTC to divert all possible power onto the LTC network to counter the attack.
3) There's a true p2pool for LTC, everyone should have it as a failover for their main LTC pools.
4) Note that wemineltc is very heavily ddos protected, due to the massive attacks near the beginning of the LTC spike. Note they are not stupid.
|
|
|
|
|
You could have a script mirror the data to somewhere that no DDOS has a hope of touching... like a google spreadsheet, or a (sub)reddit wiki....
Then there would be no point in continuing the DDOS, when it's common knowledge where the backup is.
|
|
|
|
|
