Heady Wook

Zero-JS Hypermedia Browser

avatar
Heady Wook
heady_wook@bitcoiner.social
npub1mm5h...07y3
OC Bitcoin Network: meetup.com/oc-btc/events

Notes (13)

Wife and daughter are in beautiful dresses ๐Ÿ‘— and I am walking around in this ๐Ÿ˜‚ Happy Father's Day Nostr dads image
2025-06-15 19:16:21 from 1 relay(s) View Thread โ†’
Good day, nostr:nprofile1qqsq3ppke5pel7ysw3rgl5e8lt8ky7zwavm5jrs2zx9tnu2vn5nydnqpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcvjkw67 ๐Ÿดโ€โ˜ ๏ธ
2025-04-17 16:04:55 from 1 relay(s) View Thread โ†’
The open-source mining projects have reinvigorated my otherwise timeworn interest in Bitcoin.
2025-03-15 22:36:55 from 1 relay(s) View Thread โ†’
Dear Anon, it's 2025 and we should normalize KYC-free options. While I generally recommend DEXs, there are many smaller CEXs that do not require KYC, mostly focused on BTC and XMR. On kycnot.me you can find more than 20 KYC-free exchanges: image
2025-03-12 14:06:25 from 1 relay(s) View Thread โ†’
A Cypherpunk's Manifesto by Eric Hughes Privacy is necessary for an open society in the electronic age. Privacy is not secrecy. A private matter is something one doesn't want the whole world to know, but a secret matter is something one doesn't want anybody to know. Privacy is the power to selectively reveal oneself to the world. If two parties have some sort of dealings, then each has a memory of their interaction. Each party can speak about their own memory of this; how could anyone prevent it? One could pass laws against it, but the freedom of speech, even more than privacy, is fundamental to an open society; we seek not to restrict any speech at all. If many parties speak together in the same forum, each can speak to all the others and aggregate together knowledge about individuals and other parties. The power of electronic communications has enabled such group speech, and it will not go away merely because we might want it to. Since we desire privacy, we must ensure that each party to a transaction have knowledge only of that which is directly necessary for that transaction. Since any information can be spoken of, we must ensure that we reveal as little as possible. In most cases personal identity is not salient. When I purchase a magazine at a store and hand cash to the clerk, there is no need to know who I am. When I ask my electronic mail provider to send and receive messages, my provider need not know to whom I am speaking or what I am saying or what others are saying to me; my provider only need know how to get the message there and how much I owe them in fees. When my identity is revealed by the underlying mechanism of the transaction, I have no privacy. I cannot here selectively reveal myself; I must _always_ reveal myself. Therefore, privacy in an open society requires anonymous transaction systems. Until now, cash has been the primary such system. An anonymous transaction system is not a secret transaction system. An anonymous system empowers individuals to reveal their identity when desired and only when desired; this is the essence of privacy. Privacy in an open society also requires cryptography. If I say something, I want it heard only by those for whom I intend it. If the content of my speech is available to the world, I have no privacy. To encrypt is to indicate the desire for privacy, and to encrypt with weak cryptography is to indicate not too much desire for privacy. Furthermore, to reveal one's identity with assurance when the default is anonymity requires the cryptographic signature. We cannot expect governments, corporations, or other large, faceless organizations to grant us privacy out of their beneficence. It is to their advantage to speak of us, and we should expect that they will speak. To try to prevent their speech is to fight against the realities of information. Information does not just want to be free, it longs to be free. Information expands to fill the available storage space. Information is Rumor's younger, stronger cousin; Information is fleeter of foot, has more eyes, knows more, and understands less than Rumor. We must defend our own privacy if we expect to have any. We must come together and create systems which allow anonymous transactions to take place. People have been defending their own privacy for centuries with whispers, darkness, envelopes, closed doors, secret handshakes, and couriers. The technologies of the past did not allow for strong privacy, but electronic technologies do. We the Cypherpunks are dedicated to building anonymous systems. We are defending our privacy with cryptography, with anonymous mail forwarding systems, with digital signatures, and with electronic money. Cypherpunks write code. We know that someone has to write software to defend privacy, and since we can't get privacy unless we all do, we're going to write it. We publish our code so that our fellow Cypherpunks may practice and play with it. Our code is free for all to use, worldwide. We don't much care if you don't approve of the software we write. We know that software can't be destroyed and that a widely dispersed system can't be shut down. Cypherpunks deplore regulations on cryptography, for encryption is fundamentally a private act. The act of encryption, in fact, removes information from the public realm. Even laws against cryptography reach only so far as a nation's border and the arm of its violence. Cryptography will ineluctably spread over the whole globe, and with it the anonymous transactions systems that it makes possible. For privacy to be widespread it must be part of a social contract. People must come and together deploy these systems for the common good. Privacy only extends so far as the cooperation of one's fellows in society. We the Cypherpunks seek your questions and your concerns and hope we may engage you so that we do not deceive ourselves. We will not, however, be moved out of our course because some may disagree with our goals. The Cypherpunks are actively engaged in making the networks safer for privacy. Let us proceed together apace. Onward. Eric Hughes <hughes@soda.berkeley.edu> 9 March 1993 https://nakamotoinstitute.org/library/cypherpunk-manifesto/
2025-03-10 15:53:50 from 1 relay(s) View Thread โ†’
1 terabyte hard drives for Bitcoin full nodes are dead. Minimum requirement is officially 2 terabytes.
2025-02-24 04:03:46 from 1 relay(s) View Thread โ†’
One of the friends that I got onto Bitcoin lost his phone and he never saved his seed phrase. It's just gone now. Yesterday another friend got a new phone and was angry with me and he didn't have access to his wallet. Today he messaged me saying that he had found his backup. I just helped him restore the wallet. I hope he learned his lesson. Long story short, I don't think I'm never going to onboard anyone onto Bitcoin again. People just tend to lose their shit; and don't say that it's a contribution to the scarcity.
2025-02-11 04:21:47 from 1 relay(s) View Thread โ†’
Feeling generous? Pay invoice please ๐Ÿค  lnbc1788240n1pn640qkpp5auj47yhmf4ty5t0rylu9xl8d04cr6l770vfl40upkn60pgl0fflsdz82pskjepqw3hjqsmj09c8gm6rd3hkz6mnyqkjq42ngyszsnmjv3jhygzfgsazqdfexgerw2gcqzzsxqyz5nwsp5uvyx3jr5075xtsqve54ejz7y2zz7eh7c3ct32ptxy5ndu7ae5vys9qxpqysgqlww6l8hdtqdwv32h3z7gprqfy2su362gu6zqz3udrfv995h0qyvr5dl5hwz2yw68fmfxrdavhj9q49kx52l96agdffk3c8v8ke65nrspqtn2l7
2025-02-11 03:02:19 from 1 relay(s) View Thread โ†’
Implementing a decentralized version of Samourai Walletโ€™s Whirlpool coin join protocol would require redesigning its existing coordinator-based architecture to remove reliance on a central server. Hereโ€™s a high-level approach: --- 1. Understanding Whirlpool's Current Design Whirlpool currently relies on a coordinator to facilitate the coin join process. Clients register inputs, the coordinator builds the transaction, and participants sign it. The coordinator doesnโ€™t take custody of funds but still knows the transaction structure before broadcasting. 2. Key Challenges for Decentralization Removing the coordinator without reducing efficiency. Ensuring Sybil resistance to prevent DoS or manipulation. Maintaining privacy while coordinating transactions. Minimizing reliance on a single blockchain explorer or external services. --- 3. Decentralized Whirlpool: Potential Design Approaches To decentralize Whirlpool, we could leverage one or a combination of the following: A. Peer-to-Peer (P2P) Coordination Using Tor/I2P Use a DHT (Distributed Hash Table) for peer discovery. Clients initiate coin joins directly in a P2P fashion. Nodes use Tor or I2P for anonymity. B. Federated or Multiparty Coordination Instead of a single server, use multiple semi-trusted facilitators. Shamirโ€™s Secret Sharing could be used to prevent any single entity from knowing the full transaction structure. A threshold cryptographic scheme could allow transactions to be constructed collectively. C. Bitcoin Script & Covenant Approaches Use vault-like smart contracts (e.g., OP_CTV, OP_CHECKSIGFROMSTACK) to enforce coin join conditions. Create "CoinJoin Pools" where users deposit funds and can only withdraw through pre-agreed anonymity conditions. D. Lightning Network for Pre-Mixing Before on-chain settlement, users could mix UTXOs off-chain via the Lightning Network. This avoids large on-chain transaction fees and improves speed. --- 4. Implementation Steps 1. Peer Discovery Layer Use a decentralized network (DHT, Nostr relays, or LN-based signaling). Implement a reputation system to mitigate Sybil attacks. 2. Decentralized Input Coordination Use a Zero-Knowledge proof system (e.g., zkSNARKs) to verify valid inputs without revealing them. Alternatively, Ring Signatures or Threshold Signatures could be used. 3. Transaction Construction Without a Coordinator Each participant signs their input separately. Use secure multiparty computation (MPC) to build the final transaction. 4. Broadcast & Finalization The final transaction is either broadcast by multiple peers simultaneously or via a privacy-preserving relay (e.g., FIBRE, Tor). --- 5. Potential Risks & Mitigation image --- 6. Conclusion A fully decentralized Whirlpool would likely rely on P2P coordination, zero-knowledge proofs, and multiparty computation to remove the need for a trusted coordinator while preserving privacy and efficiency. It would be a complex but highly valuable upgrade to Bitcoin's privacy ecosystem.
2025-02-11 02:33:44 from 1 relay(s) View Thread โ†’
Todays Assigned Reading: File Drop: The UBAR2 3D Printable AR15 Lower Learn a skill. Make a thing. ctrlpew.com/file-drop-ubar/
2025-01-18 19:56:14 from 1 relay(s) View Thread โ†’
nostr:nprofile1qqs8v3q3nvvwc444kfmeurgrtem392wkd8dlhedjch693j6kftake9gpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhs7rm3jp New York (reversed seared), leftover homemade mashed potatoes with beef roux gravy, and boiled/blanched broccoli image
2025-01-05 01:53:13 from 1 relay(s) View Thread โ†’