It has to be a mistake and someone's very, very, sorry now. Happens every now and then.

One roadblock to solo mining seems like it should not be one: the memory/disk requirements of a full node. It sems to be that, in order to mine, you need just the latest N blocks (enough for the block template, and a few more to handle reorgs). Also the tx pool. But most of the DB, you don't need if your goal is just to mine. So making a "mining node" mode may make being a solo miner less painful.

Edit: pool hash now down to 60%, and fee down to 4% (from ~80% and ~9% this morning).

BCT logged me out and ate all my lovely point by point prose, and I'm not going through that again, so here are just some main points I remember:

- binaryFate reports trading worked, it did not for me. I ended up with a bid and ask both at 600 for mead (only one of them was mine).

- when in the command line, it needs a list of commands handy. Also needs to understand names, there's no way to tell someone's ID, the player list is gone.

- the number of items owned should really be in the item page, so when you type a SELL/BUY/GIVE command, you can see it change (or not). I found I constantly switched pages to find out things, and it becomes tiring quickly. Relevant info should be on the page.

- command response seems to use only the first world in a name: I gave some mead to 5, which seems to be New Liberty, since the response told me I have them to "New".

Edit:
- also wrong years in some items, I've lost the list, but my suits at least were wrong, and CUL points IIRC. There were more.

Done. The estimated pool share now has an extra "X/Y blocks" as an explanation.

Pool's now at 66%, going down from the earlier 80%.

 Estimated pool share: 78.3%

This estimation uses the actual blocks found. The pool found 47 of the last 60 blocks. As a few people mentioned above, the "network hash rate" is an approximation that can lag until the difficulty algorithm overcomes its inherent inertia.

The variable fee system is now in place. Current pool share is 50 of the last 60 blocks, but slow blocks mean that some large miner has recently (temporarily ?) stopped mining.

Took a few hours of work, but it's done. Not used to Javascript.

My pool now estimates its share of the total hash (currently about 60%), and displays the effective fee (currently same as base). The hash rate estimation is done from the recent blocks found, so should not lag behind difficulty as it currently does.

I'll put that on github when it's switched on tomorrow and confirmed to be working well.

This is advance notice that in a bit more than 24 hours, my pool will switch to a variable fee system:

When the pool hash rate grows past 50%, the fee will start growing as 1% extra fee for every 5% of the network hash rate. So base fee being 2%, 60% of hash rate will cause the fee to jump to 4%. 100% hash rate will bump it to 12%. Both the pool fee and the donation get scaled the same. When the pool hash rate goes back down, the fee automatically goes back down with it. The above formula is not set in stone, I may need to tweak it depending on how it goes.

If your ISP has spied on your connection (and let's face it, they prety much all do, whether for themselves or on behalf of people they can't easily say no to), and thus know which blocks you have received, any output used as input to a ring signature can be ruled out as yours if it was created in a block you did not download. Till we get I2P anyway.

Being a cunning linguist may allow you to tokenize and parse a complex text into an adequate syntax tree, but you still need domain specific knowledge to derive proper semantics from it.

Accounting is done. 481 AEON went missing in those txes that were mined on the wrong fork.
The relevant addresses for those have been found, and missing balances paid. Amusingly, it needed a single tx for all 16 miners:

http://chainradar.com/aeon/transaction/fa45c15cd76f73e6e1bbc401c8582646b3f07f23895a7715f3208f8426ec86dd

Payment ID: echo -n "aeonpool.mooo.com failed txes" | sha256sum

Sorry again for the trouble, and make sure to give Arux's pool some love too

After some dread, I've restarted the pool publicly with 0.9.4.0 and it appears to be working well. It's found blocks already and made some more automatic payouts, and the blocks were accepted by smooth's daemon. So it looks like it's all back on track after reverting blockchain and daemon.

There's a silver lining though, Arux's pool now has 20 kH/s

I'll be doing the accounting for missing payments this afternoon.

Due to the fork yesterday, the pool payments also got wonky.
There are a number of payments made by the pool yesterday and today which are not included in the correct chain, and thus miners did not receive these, but the pool does not know that, and the txes do not seem to have been reincluded in another block. This means I will have to go manually tally up all that the pool thinks was sent, but was not actually included on the main chain, and send manual payments to miners for that missing amount.

In the meantime, please use Arux's pool (http://52.8.47.33:8080/) or solo mining from the daemon.

Sorry for the inconvenience.

Yes, that branch is what my pool runs. Note that it has other random stuff merged from other places, but it's known to be working (well, as a matter of fact, it's known to be broken just now, but nevermind that).

That's the Wolf miner, which only works with AES-NI.
The one that works without it is https://github.com/iamsmooth/cpuminer-multi

The pool software has a README with the list of steps you need and the prerequisite versions (mostly redis and mode 0.10).
The patches for cn-light are in https://github.com/moneromooo/cryptonote-universal-pool

Hi, my pool is currently unable to mine. Not sure exactly what's going on, the daemon rejects mined blocks, even though I've reverted blockchain and daemon to earlier versions.

Please mine on http://52.8.47.33:8080/ which is Arux's pool for now.

Has this been done before we move to "final" credentials ?
Throughout, or at least for login and anything that has potential to write to the DB.

Just a note to say that my pool appears to be comfortably past 50% at the moment, and that while I'm not planning on 51%ing aeon, you wouldn't just trust some guy on the internet not to, right ?
While Arux's pool appears to be down, the daemon can solo mine, which should still be a reasonable option for large hash miners that can handle the RAM usage.

Incomplete unordered list of things that would be useful:

Connection via https/ssl/whatever
Ability to know when someone enters, leaves, and/or says something in a particular building
Read access to properties of buildings, characters, and other interesting things
Ability to "appear" as a character (albeit one that may be controlled by a program)
Write access to relevant properties of the character the program controls
Ability to move the character to another building
Ability to say somehting in the current building's chat
Ability to transfer things between the program character and another character [1]
Ability to enumerate characters and things in a particular building

[1] This introduces an interesting point about permissions: if someone codes a trading bot, CK has to somehow decide whether the bot's commands to transfer stuff (presumably based on a chat line from another player, such as "buy W11600 for 1M monerito") is consistent with that player's wishes.