I understand now! That is a neat feature!
Maybe start them off nostr:npub1xkere5pd94672h8w8r77uf4ustcazhfujkqgqzcykrdzakm4zl4qeud0en and let River hold it until he learns how to self custody. Also Bitkey has a noob proof solution nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m . Also nostr:npub1cn4t4cd78nm900qc2hhqte5aa8c9njm6qkfzw95tszufwcwtcnsq7g3vle Strike can onboard and educate your friends. Keep going!
No kyc only
Like the ones that use email?
Key Manager in Passport fixes this.
https://docs.foundation.xyz/passport/passport-menu/settings/extensions/#key-manager
Love it and I understand Passport is user friendly; still not ideal for these buddies I mentioned lol
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.
I just had my first 6,718 blocks ago at block 876,533:
https://mempool.space/block/00000000000000000000355580dc19cb919cd6057bc72fca329a49ea92ae9ef3
Feeling generous? Pay invoice please 🤠
lnbc1788240n1pn640qkpp5auj47yhmf4ty5t0rylu9xl8d04cr6l770vfl40upkn60pgl0fflsdz82pskjepqw3hjqsmj09c8gm6rd3hkz6mnyqkjq42ngyszsnmjv3jhygzfgsazqdfexgerw2gcqzzsxqyz5nwsp5uvyx3jr5075xtsqve54ejz7y2zz7eh7c3ct32ptxy5ndu7ae5vys9qxpqysgqlww6l8hdtqdwv32h3z7gprqfy2su362gu6zqz3udrfv995h0qyvr5dl5hwz2yw68fmfxrdavhj9q49kx52l96agdffk3c8v8ke65nrspqtn2l7
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

---
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.
I see you now, it also used your lightning handle as walking smoke
I found me! It took my lightning handle!
I paid for one. I don't see myself there either
I absolutely despise mosquitoes 🦟 and other blood sucking insects. They are parasites.
Todays Assigned Reading:
File Drop: The UBAR2 3D Printable AR15 Lower
Learn a skill.
Make a thing.
ctrlpew.com/file-drop-ubar/
Guess #1 was good?
New York (reversed seared), leftover homemade mashed potatoes with beef roux gravy, and boiled/blanched broccoli 
What are you drinking/eating? Or what music are you listening to?