Several things to think about, weak points could be:
Domain name, since the registrar will probably have your information. Namecheap allows bitcoin payment, but I think they still require contact information. Going with an onion url would limit that impact.
Hosting, again, they will almost certainly have your information. Swisslayer allows bitcoin payments, but contact info might still be required. Could be mitigated by going with Tor or some other service, but that limits discoverability.
Server software -- you would want to limit the ability to be compromised, so something like OpenBSD with the built in httpd and raw html files would be a reasonable bet for preventing intrusion. Keeping it simple would leave less attack surface, and less potential to leak information.
Using Tor to connect would mean less logs between.
Any information you gave in content could be used to trace, but that is difficult and would require being careful in the writing style, and what information is leaked in that channel.
EDIT: As beefhash points out, piggybacking on an already accessible public endpoint negates a lot of the leaking of your information through your own services.
Comments
Several things to think about, weak points could be:
Domain name, since the registrar will probably have your information. Namecheap allows bitcoin payment, but I think they still require contact information. Going with an onion url would limit that impact.
Hosting, again, they will almost certainly have your information. Swisslayer allows bitcoin payments, but contact info might still be required. Could be mitigated by going with Tor or some other service, but that limits discoverability.
Server software -- you would want to limit the ability to be compromised, so something like OpenBSD with the built in httpd and raw html files would be a reasonable bet for preventing intrusion. Keeping it simple would leave less attack surface, and less potential to leak information.
Using Tor to connect would mean less logs between.
Any information you gave in content could be used to trace, but that is difficult and would require being careful in the writing style, and what information is leaked in that channel.
EDIT: As beefhash points out, piggybacking on an already accessible public endpoint negates a lot of the leaking of your information through your own services.
Is there a reasonably easy way to get anonymised bitcoins? Mining is currently out of the question, purchase on exchange will leave a trail.
Just use Monero?
Trade bitcoin locally face-to-face.
I've used https://localbitcoins.com.
Localbitcoins requires KYC these days.
You don't even need to register to use localbitcoins, they only require KYC to put up a listing.
Monero and xmr.to!
1. Create JS library.
2. Add bitcoin-wallet-stealing code.
3. Upload to NPM.