G'day everyone,
Joshua Marriage (@satoshua everywhere) here, the creator of HIBK.
Thanks OP for sharing my site, any chance you remember where you came across it?
Lots of great questions here (most are covered in FAQ on the site) pointing to less-technical users, so let me explain a few things.
How to use HIBK:1. Paste BTC address
2. Check txs for privacy gotchas
3. Discover obfuscation resources
How HIBK works:1. Request made to Blockstream's Esplora API to get recent transactions for address
2. Response with JSON data for those transactions from blockchain received
3. Privacy analysis script runs client-side in your browser to find 'privacy gotchas'
Few important technical points:- HIBK is a static site hosted on Github Pages, so there's no server side processing.
- API requests, responses, and privacy analysis all take place locally in the browser.
- No tracking scripts or any nonsense like that, and everything is open source.
And a few 'marketing' points:- No reflinks, never will be, at most I'll offer "Surveillance ≠ Sound Money" merch.
- I ran HIBK by BTC privacy OGs like Matt Odell and 6102bitcoin upon publishing.
- I've taken my inspiration from Troy Hunt's amazing Have I Been Pwned.
While on 'marketing'...
- Sousveillance: these links are to block explorers that help you better understand tx privacy
- Mixers and CoinJoins: tools (mostly wallets) that run implementations of privacy protocols
- Chain Hopping: non-KYC exchanges brought to my attention by @notsofast on twitter
I've noticed some confusion around how HIBK would determine whether an address is currently surveilled. That's not my intention, the idea is to help people to learn about 'privacy gotchas' that would lead to their address being "likely known to surveillance." These 'gotchas' are documented in detail by bitcoin privacy pioneer Chris Belcher (he's the dev funded by Human Rights Foundation to build out CoinSwap) on the bitcoin wiki.
Point being, if you're getting sloppy with your bitcoin opsec, chances are you're already known to blockchain surveillance companies. They tend to take a 'catch-all' approach, much like NSA practices popularised by the Snowden revelations. The most alarming thing when it comes to bitcoin, is the immutability of the present, past, and future. Prevention is the best cure and 'privacy gotchas' are the dots that surveillance companies join to eventually find some KYC transaction, or something else unsavoury.
I invite everyone to check the source code and even run the tool with Dev Tools Console open to see what queries are made. No data is stored and there are no connections to databases. The only 'database' as such involved is the bitcoin blockchain, of which I am querying through the Esplora API. That being said, is the reason I have a notice recommending you use a VPN, as I am unaware of what logging may take place at the infrastructure level by GitHub, and further on, by Blockstream.
Keep in mind this is barebones v1 and my hopes are to help publicise the importance of bitcoin privacy, because
Surveillance ≠ Sound Money and it doesn't do the "bitcoin as a store of value" narrative any favours. Really appreciate everyone's feedback and my apologies if I haven't touched on your questions/assumptions here, I'll try to hang around and cover any other concerns.
Cheers!
LINKS:HIBK:
https://haveibeenknown.com/FAQ:
https://haveibeenknown.com/faq/GitHub:
https://github.com/satoshua/haveibeenknown (open source and deployed to Github Pages - see 'Environments')
Privacy Analysis:
https://github.com/Blockstream/esplora/blob/master/client/src/lib/privacy-analysis.js (this script runs locally in your browser)
Blockstream Block Explorer:
https://blockstream.info/Blockstream's Esplora API docs:
https://github.com/Blockstream/esplora/blob/master/API.mdList of non-KYC @notsofast showed me:
https://kycnot.me/