Turns out, you have to prefix the private key with "p2wpkh:", or else it imports it as a legacy key, and generates a completely different public hash.
If you just paste the raw key, Electrum uses a legacy format, and none of the transactions show up for that private key. Adding the "p2wpkh:" prefix to the key makes the transactions show up, but I realized that well after someone else claimed it.
I don't know if this is an Electrum thing, if this is considered general knowledge now for those who regularly use BTC, or if it's a quirk of how BTC has evolved.
redactsure•3h ago
Demo Signup: https://app.redactsure.com/ Bitcoin Checker: https://redactsure.com/bitcoinchallenge/
Limitations: - 15mins per session (why? GPU per session, limited spots) - US only is preferred (why? latency, I am streaming video to you) - No mobile, keyboard required - Requires you to verify an email
Some people were asking about implementation I'll provide a few details. - A server hosted browser - I manipulate what you are seeing on the webpage in real time - While I don't change the underlying webpage I do manipulate your actions to the webpage - A full transformer model runs in real time along side you (tries to find all sensitive words you see)
Overall the systems goals are to allow you to perform work without ever seeing the data. It's in a early prototype stage and I expect a large numbers of edge cases just from the nature of the problem. The bitcoin is a proxy to the real goal which is protecting real PII in remote work settings.
Other notes: - It would be nice if you tell me the bug. I would like to post how you broke it. - I'll post updates as well as info on bugs sessions here: https://x.com/CharlesCurt2