[0 GH/s 0% fee SMPPS] ArsBitcoin mining pool!

[BurningToad]

Yes, apparently gentakin is trying to demonstrate that he can have fun at our expense.  Stats page is down for a bit. (Client side scripting in nickname to throw a popup.)

*Edit* XSS fixed, stats back up.  

[gentakin]

Sorry if this caused any troubles. It was just an alert() after all. Not trying to have fun at your expense.

My intention was to let you know about that bug in your stats before a bad guy exploits it. Please take my apologies.

[BurningToad]

Alright... I forgive.  However, you could have just PMed me without causing problems for my users who are trying to view the stats.

[fpgaminer]

After disabling timestamp updating on most of my miners (instead of just one experimental one), I'm getting 1-2% rejected (compared to 5-6%). So I guess this confirms the Bitcoins.lc solution, which suggests that poclbm's support for X-Roll-NTime is broken somehow.

So that's certainly better but I'm still getting those random shares that are being rejected for no reason (probably duplicate work). There are two relevant patches I found that are server-side related:
http://forum.bitcoin.org/index.php?topic=14483.msg208046#msg208046
http://luke.dashjr.org/programs/bitcoin/w/bitcoind/luke-jr.git/shortlog/refs/heads/getwork_dedupe

[BurningToad]

Thanks! I'll look into it this weekend.

[fitty]

yahhhhhhhhhhhhhhhhhhhhhhh. I was asked to post that I won the 1st bounty. I hope the next block comes easier. =)

[goldcd]

yahhhhhhhhhhhhhhhhhhhhhhh. I was asked to post that I won the 1st bounty. I hope the next block comes easier. =)

Congratulations - you complete jammy bastard

[shamen]

^ this

[fitty]

yahhhhhhhhhhhhhhhhhhhhhhh. I was asked to post that I won the 1st bounty. I hope the next block comes easier. =)

Congratulations - you complete jammy bastard

I felt a little bad a few guys put in a lot more work. Not sure who bg is but he was there early with a really nice setup. I was battling it out around 6-9th most of the block, mostly with 4x5870. 

Honestly I thought the pool was broken or cursed. I don't think I would have lasted much past 3 million thankfully it never came to that. =)

[FreeJAC]

yahhhhhhhhhhhhhhhhhhhhhhh. I was asked to post that I won the 1st bounty. I hope the next block comes easier. =)

Congrats again man! Well done! Here's hoping I get the next one!

[BurningToad]

Hello, you need to use http://arsbitcoin.com to log into the website now.  The pool.burningtoad.com will no longer work. You can still mine at that address though.

[fpgaminer]

Wow, this pool has been crazy lucky after that first monster round. 4 blocks now! WOO!

[BtcNmcMiner]

Probability is now in our side!

[goldcd]

Wow, this pool has been crazy lucky after that first monster round. 4 blocks now! WOO!

That was a pretty nice surprise to wake up to.

Although thinking how many those couple of guys with proper mining rigs just picked up (yes, I mean you ampeater).. *JEALOUS*
I can always find the bad side

[shamen]

Sometime overnight my password stopped working for this pool. I had it saved in my browser and this morning (UK time) it was no longer valid (where it was last night). I tried to enter it manually and got the smae result. I thought maybe I had saved it/remembered it wrong until another pool member came into IRC to report the same problem - his password stopped working overnight

To be a bit safe, I then tried multiple logins with the incorrect password until the server reported my account was locked.

I dont know if there is a security issue or a glitch. However I have checked this end and there is no malware.

I run:

- Avast Free
- Malwarebytes Anti Malware
- Embedded Linux hardware firewall / NAT
- Physical linux firewall with NAT, transparent proxy and full Network Intrusion Detection
- Windows 7 (mining rig) installation is 7 days old on a brand new HDD and is not used for anything other than mining related activities.

My other location (where I sometimes log in from) is

- Ubunty Natty
- NIDS on machine
- Junpier firewall

irc log

[12:46] == pimpinganiteasy [~candyman2@pool-*REMOVED*] has joined #arsbitcoin
[12:48] <pimpinganiteasy> i cant login
[12:48] <pimpinganiteasy> can someone fix this
[12:54] <shamen_> ive got the same problem mate
[12:54] <shamen_> tried to log in this morning and my password was invalid
[12:54] <pimpinganiteasy> wtf
[12:54] <shamen_> (same password i had saved in my browser from yesterday)
[12:54] <shamen_> something smells wrong
[12:54] <pimpinganiteasy> yes
[12:54] <pimpinganiteasy> something is
[12:54] <pimpinganiteasy> whats the odds
[12:54] <shamen_> to be safe, I logged in repeatedly with the wrong password until myy account was locked
[12:55] <shamen_> id suggest the same
[12:55] <shamen_>
[12:55] <pimpinganiteasy> yes

Is anyone else experiencing this? If you are already logge din can you log out and log in again with your password ok?

*edit* Aexoden reports his works fine. Hopefully the problem is just something silly and nothing to worry about

[13:31] <@Aexoden> My login works fine, so if something's wrong, it seems to be either with your account or the browser saved it wrong or something. You'll have to wait for BurningToad I guess. Try deleting your cookies from arsbitcoin.com and trying again. Well, unless your account is locked now.

[goldcd]

Seems fine for me.
On a vaguely related note, I was using the same password on slush as I did on MtGox (yes yes, I know).
Anyway, seemingly somebody tried to alter my payment address on slush - I have a non-dictionary password, so somebody has been hashing.
Unlikely to be the case, as I think arsbitcoin does same as slush and mails you through confirmations when somebody has tried to change something.
Actually - not even sure what the point of this post is now...
...basically, I'm fine. It's just you.

[simplecoin]

I'm honored to see my pool front-end being used by the Ars crowd

Best of luck!

[bitblazing]

I cant login either!

[shamen]

I cant login either!

So the count of 'unable to login' is up to three members.

(btw, ive never been a member of mtgox)

[shamen]

Burningtoad has found the issue. Looks like its relating to some work he did last night, and is fixing it now

[14:47] <@BurningToad> i'm looking into it, the problems are due to an update I did last night, doesn't seem to be anything serious, working on a fix

*edit* back in now. all working fine and everything asit should be. Big thanks to burningToad for the prompt fix!