There is now a monero tipbot in #monero, tippero, kindly hosted by fluffypony.

It is coded from scratch, but works in the same way as typical IRC tipbots. See !help and !commands for more info, how to use it, etc.

If you spot any bug, feel free to ping me.

Can you be more specific ? The pool is running fine just now, and there are others mining on it, as already mentioned.

Are you talking about the web frontend, or the mining port, or both ?
In both cases, what form does the "can't access" have ? An error message, or timeout (which one, by what software ?) The current pool IP is 86.160.41.211, in case you're getting a wrong resolution. Mining is open on port 5555.

Nobody was banned on that pool.
It could be that your ISP has a lot of lag in updating DNS, as the pool's IP address changed a few hours before your post (because my ISP likes to be a pain I think). Normally the new address propagates with 10-15 minutes but it's possible your ISP took a while to update.

On another note, I also get a white page for the website, with Firefox. With white text, which only visible if you select all text.

Nope.

Two more tries.

The blockchains are separate, so if you just run both mainnet and testnet, it'll be fine.


That means the daemon either did not find the blockchain, or disliked it for some reason. You should have files called data.mdb and lock.mdb in a testnet subdirectory from wherever your mainnet blockchain is. If you were running mainnet before, I suspect you converted the mainnet blockchain, but not the testnet one. Add --testnet to blockchain_converter if you did not do it.

Note that there are known bugs at the moment which make that DB development branch mostly unusable.
In particular, you most likely won't be able to send anything. It's still very much work in progress. I suggest using a testnet wallet if you want to play with it.

have a problem with the wallet here. I seem to be unable to send anything, even after rescanning from scratch. Any tx seems to be rejected by the daemon, claiming the outputs are already spent. This started after I did another round of dust consolidation which large split txs (I'm not sure if this is the reason or just chance timing). Most of the balance is now unlocked, but it can't be used it seems.

So I suggest that people stop mining at my pool for the time being till I work out what the problem is, as I am unable to send anything

OK, it seems fixed. The local pool state was shot to bits it seems. I could now send the txs, and then the pool payouts should follow. Not sure why the pool state got corrupt though. Phew, got a scare here

Pool updated with the latest git. Fees back down to 1.5%. Compiled Fedora binaries updated at http://dbpool.mooo.com/doctorbyte.tar.xz.

It's not the main blockchain branch. This is my own branch. The one you want to look at is: https://github.com/tewinget/bitmonero/commits/blockchain

At doctorbyte's request, I placed Linux (Fedora) binaries of that latest version at http://dbpool.mooo.com/doctorbyte.tar.xz. This contains the daemon and wallet. No guarantees they work for anyone, especially anyone not running Fedora. If not, you'll be better off building from git (encouraged for all anyway).
The pool is now running those binaries.

Sorry, my daemon crashed overnight. It's back up now.

I'll be updating to the latest code this morning. I'll bump the fees by half a percent to cater for the increased tx fee. I'll also decrease the expected time to share as I think the current setup makes for large variations in payout distribution as some blocks are solved so fast that only one miner gets to submit a share for it.

So the pool seems to have not liked the restart/resync and thinks it's found 9 different blocks for height 12774
I hope it won't break when they mature.

Anyway, could you point me to the code where Doctorbyte uses more stealth addresses ? I looked, but did not find anything.

I've just opened 7878 on my firewall, it was closed.
Restarting the daemon now, it seems to be redownloading chain, not sure what's going on... But you should be able to connect to it soon.

It's connected to 176.57.143.70 at the moment, the only peer.

Edit: daemon running again, should be reachable now on dbpool.mooo.com:7878. The pool seems to be moaning about blocks higher than the chain height which is a bit worrying. Hopefully will sort itself out
I'll be keeping an eye here in case there are still issues syncing.

Aaah... I see the problem, it's mooo, not wooo

And you don't want to access it via IP directly, the ISP tends to change the IP every few days so your miner will only follow if you use the domain name.

Can't do that, they're pool miners. You could run your own pool though, but then you'd run into the same thing.


Oh, what did you change to the ring signatures ? I thought there were just changes to the emission config.

start_mining <address> <threads> in the daemon.

For the pool hash rate, it counts an average of submitted shares over the last... 20 minutes I think.
If you've waited at least that long, then it does sound odd if it never goes above that.

Blocks found stay maturing for 60 blocks, so you should see your pending balance increase after a found block you hashed for matures (and is not an orphan). At the moment, it takes about 1 hour and a half. See
http://dbpool.mooo.com/#pool_blocks for the list of blocks, and you can get an idea of when a block you hashed for matures.

Sure, I wasn't saying it's broken. The jump in hash rate was certainly a sudden cliff.
The network hash rate was staying within 1.8-1.9 kH/s, it's started to go up now, currently 2.4 kH/s, so it looks like it's working

I think the difficulty update algorithm is a bit slow to update.
The pool has about 5 times the nominal hash rate of the whole network.
This is caused by the difficulty being slow to increase after a sharp increase in the real hash rate.
We're getting a block every 8 seconds here at the moment, compared to the expected 40 seconds average.
It'll be interesting to see when the difficulty algorithm catches up.
We're also getting a number of orphans, presumably due to the fast block time. An interesting test bed for cryptonote.

For the information, I just found my first block, and the block reward was 4.39.

At 40 seconds per block, that's about 9500 coins per day.

If you still can't sync after delete p2pstate.bin, I guess you can try the pool instead

I know deleting it solved it for me.