Well, the thing I remember being linked to was on Reddit. I found this, but I don't think that's the one I had seen:

http://www.reddit.com/r/BitcoinMarkets/comments/25mpbf/hitbtcs_volume_is_very_suspicious/

Now, I have no experience with them, so that's just hearsay (and even if I said I had, it's be hearsay for you )

I don't know about Hitbtc, but Poloniex shows their volume history. Click on "1 day" and "1 month" on the graphs, and you can see the daily volume for the last month. I'd say it averages about 2 bitcoins a day on Poloniex, very roughly, but with high variance.

I would say Poloniex, unless you want to stay anonymous. Hitbtc was said to be possibly faking their volume, but Poloniex now requires your name and country to withdraw. Apart from that privacy thing, Poloniex seems quite trustworthy.

In fact, you can already use OpenAlias to withdraw your XDN from the luckyducky (the tipbot/gamebot on Freenode #darknote and #digitalnote) if you have your domain name setup with an OpenAlias XDN address). Dice and blackjack betting for XDN, bets from 10 XDN to 1000 XDN

On another note, minerjoen's issue was indeed trying to connect just when I was updating, it's all working fine now.

Problems with very high orphan rate is usually due to your computer's timekeeping not agreeing with the rest of the network, and the network rejecting your blocks.

Check your time against NTP. Computers sometimes drift a lot and need to be kept synced regularly to compensate.

You might have caught me in the middle of the pool update

I just updated the pool to the newest, and it did not go smoothly. All fixed now, phew!

Mining ports are 2222, 6666, and 8888. 8080 goes to the website, the usual 80 port also works, 8080 works for historical reasons

If you're running a CPU miner,

./minerd -a cryptonight -o stratum+tcp://duckpool.mooo.com:2222 -u YOURADDRESS -p x -t NUMTHREADS

That ought to work just fine now that my battle with the pool update is finished. I just tried this command (with my address and 1 thread) and it works. Let me know if not and I'll try to help.

New version of the monero wallet generator at https://github.com/moneromooo-monero/monero-wallet-generator.

It can now display seeds in Japanese and Spanish (you will need my latest patch to simplewallet to restore them, however. Moreover, it might not work yet on Windows, I'm told there are UTF-8 issues there with the seed).

GPG verification instructions are now on the page, and a standalone signature is there for those who do not get the file from git.

And last but not least, there is a vanity address generator
It's pretty basic, and does not check whether a particular prefix makes any sense (yet).
Chances are pretty good it'll be pretty slow though. So to get a sense of how fast it goes on your CPU, try it first with a small prefix. And remember that it it's a prefix that can't be generated for an address, it'll never find a suitable address.

Actually, there is one caveat:
The view key will catch all outputs that go to this address, and this includes any change from transactions out this address may have made.
Thus, the final balance is an overestimate due to (1) any transactions out being not seen, and (2) any change from these appearing as a payment.

Curious how much monero the core team donations wallet received ?

Now you can look!

With latest git:

./build/release/bin/simplewallet --generate-from-view-key 46BeWrHpwXmHDpDEUmZBWZfoQpdc6HaERCNmx1pEYL2rAcuwufPN9rXHHtyUA4QVy66qeFQkn6sfK8a HYjA3jk3o1Bv16em:e422831985c9205238ef84daf6805526c14d96fd7b059fe68c7ab98e495e5703:/home/user/monero-core-team-donations-watch

refresh

Enjoy

Good catch, I fixed the web page to say 10 too, thanks.

I've just updated http://duckpool.mooo.com with that change.

There might be a little problem here.

My daemon is not accepting block http://chainradar.com/xdn/block/7861e683a259f0050543b923770b3595e3e900cd4009bb3e108140f12890b66c

2015-Jun-18 23:31:35.896566 [P2P3]Block <7861e683a259f0050543b923770b3595e3e900cd4009bb3e108140f12890b66c> has wrong major version: 1, at height 136214 expected version is 2

I'm guessing there's more hash on the old version and they build upon the "wrong" chain. Looking at the code, it seems there's possible been enough hash on the new chain for the upgrade detector to trigger, but I'm speculating here, I've not looked at it much.

I'm not going to hack that check out for now, in hopes that this will resolve itself, but AFAICT this can only happen if new daemons come online and hash on the partial chain.

That looks more like expected.
The first set of errors are for UDP, I believe.
The second one, about binding, I do not get here. Though I'm surprised it binds to 0.0.0.0, it should bind to 127.0.0.1. I tried setting 0.0.0.0 and it still works fine though. Does it work without torsocks (I guess you can pull the network cable to make sure nothing monero goes out) ?
In any case, a strace log would let us know what syscall is failing, and with what error.

About as safe as a piece of string is long, I'd say.

Now, if you have a more precise question, a more precise answer might be found.

Now, this is hilarious. I had this... can't be that... moment...

But it is. You are using the original bitmonero fork from TFT

You want https://github.com/monero-project/bitmonero

What version are you running (git commit hash) ?
Modified or not (I don't see a hash with "b566" in my tree) ?
That "Starting..." message is only in the blockchain conversion utilities on my tree (master from yesterday), which seems odd.

I just tried running vanilla bitmonerod with torsocks and I can sync fine. I'm getting failed connections after syncing though, but this is encouraging as I think most/all of the net code goes through the same lib (epee).

I might have a go at seeing what's going wrong depending on time available.

http://getmonero.org/getting-started/merchants

(it's not only merchants despite the url)

That is curious. I just did this same command and it worked fine.
If you downloaded the file via github's web interface, make sure you got the "raw" file, and not an HTML wrapper. The file itself should be 3144 bytes.

After that:

git clone https://github.com/moneromooo-monero/monero-wallet-generator.git
cd monero-wallet-generator/
git show --show-signature

You should see "Good signature from..." with my key (4D6CEFC3). You will get a warning that the key isn't trusted, and that's expected, since you did not tell your gpg to trust my key.

Since the file ended up hosted on saddam's server, I will GPG sign the file itself as well for next version, so people don't have to use git for this.

Thanks! And to others who sent some too