They are included in the readme.txt in miner archives (for your verification).

Dropbox is periodically down because somebody periodically DDoSing it. There is alternate location:

https://mega.co.nz/#F!h0tkXSxZ!f62uoUXogkxQmP2xO8Ib-g

Donation addresses:

PTS: PZxsEQoiMeB6tHcW2ZySBEiCPio1WkxbEL
XPM: AW2388DEWNEfMH4rP9kcj9yKcMq1QywYT4
DTC: D6PmUogMigWvXurgFTqm5VLxQeVpXdYQj3
LTC: Lby4YjhcAxhmbsdHFb4nYydrwGoiJezZt1
BTC: 1FxekeK5La7AuF3oxiLzPKnjXyLMrux6VT

Double-check in readme.txt before adding.

yvg1900

I am curious why not to place a call for donations for miner developers whose software you are pointing in the tutorial?

yvg1900

Max, I am perfectly aware of the change, my question relates on the conceptual details on the adding checkpoint at this time. Isn't that too early? What is the checkpointing policy? Shall other users be enforced to update the wallet S/W? These are questions, not the code change.

Checkpoints used to serve kind of performance shortcut to bypass some DS verifications, if I am right. Then the question is there any serious perf impact at this block height?

yvg1900

Any details on checkpoint?

yvg1900

So far so good.

As a developer of miner mentioned in the guide, I can tell - well done. So, the guide is "Miner Developer Approved"

For those who download miners - I would also ask to verify authencity of the miners using md5sums.txt and md5sums-signature.txt - you can do that right in your QT wallet with File/Verify Message function. Try advanced functions of your wallet, maybe you will need for something else

Good luck mining,
yvg1900

There are numerous claims bter admins do not respond to support email, but contradictonary reports on the withdrawal matter. Some get withdrawals delayed.