pull down to refresh
Look, convenience almost always comes at the expense of true ownership. WoS has been amazing for beginners and small coffee payments because you never had to worry about channels, liquidity, or routing. It just worked.
But handing users a 12-word recovery phrase doesn’t automatically make it 'self-custodial' if moving your own money still depends on a small group of operators giving you the green light. Calling a federated setup 'Lightning self-custody' is confusing for everyday users and waters down what real Bitcoin custody actually means.
If you need someone else’s green light to move your sats, it’s not your keys.
You might be right on the money here. Even if it never becomes the global reserve currency, simply functioning as an unconfiscatable safe haven for those who value it is huge. Makes me look at the whole question from a much better angle.
That’s a tough pill to swallow, but maybe that's the reality. Does sound money actually need the promise of getting rich to win people over? If greed is the only engine driving adoption, it really makes me wonder what we’re actually building here.
Hard forks and dev drama come and go, but if the price never moons and it's just neutral money, would I still care as much as I think I do? That's just one of the many questions I have in mind. Still trying to figure it all out.
Then we’d have a much bigger problem. One sat will always equal one sat the real question is what that sat can buy.
This is exactly the kind of small, practical Bitcoin tool I enjoy discovering.
After experimenting with solo mining and learning that my laptop would statistically need around 8.6 billion years to find a block, I started thinking less about chasing improbable rewards and more about tools that make Bitcoin genuinely useful. This project fits that idea perfectly.
I opened it on desktop, and the setup is impressively clear: loan terms, amortized or interest-only payments, BTC collateral, margin-call and liquidation thresholds, payment schedule, and JSON backup. Keeping the data in localStorage is also a sensible privacy-first choice for a personal agreement between friends.
A useful future addition could be a timestamped BTC price source and an exportable agreement snapshot that both parties can sign. Optional multisig escrow would make it even stronger without turning it into another centralized lender.
Transparent rules between real peoplethat feels much closer to Bitcoin’s original spirit. Nice work.
I tried solo lottery mining on my laptop. It submitted accepted shares, but the estimated time to find a block was 8.6 billion years 😄 You do have a Jetson, so it could still be a fun Bitcoin mining experiment. It just wouldn’t be profitable.
That makes sense learn the operational lessons on cheaper hardware before committing serious capital to new ASICs.
Beyond the machines themselves, which hidden cost surprised you most when scaling: power, cooling, downtime, repairs, or something else?
Point taken. I’m starting to understand the difference. The small cost makes me think twice before adding noise, and anything earned afterward is simply a bonus. Lesson learned.
Today I learned a small but important Stacker News lesson: posting and commenting aren’t free, so I’m trying to slow down and contribute something useful instead of replying everywhere.
For longtime stackers, what helped you most when you first joined: writing original posts, joining discussions, or simply reading and supporting good work?
The fixed supply is what caught my attention. I’m building a Windows application by myself, so I know how quickly one simple idea can turn into dozens of design decisions.
One thing I’m curious about: when new players start, do they understand that every trade only redistributes existing money, or do they still expect the game to create more somewhere?
I haven’t played enough ticks to offer useful criticism yet, but that’s the first thing I’ll pay attention to.
Hi Alejandro. I’ve recently started working alone on an early-stage project. It’s still too early to share the details publicly, but I’m building it from the ground up.
From your experience building and scaling mining operations, what is the most important assumption a solo founder should test before investing heavily in infrastructure? Looking back, what would you validate first if you were starting again today?
That’s what surprised me most. My mining experiment wasn’t completely useless. It taught me about pools, shares and difficult. But SN showed me the human side of Bitcoin.
Here, people learn from each other and support useful contributions with real value. That feels much more rewarding than watching accepted shares scroll past on my laptop.
Thank you. I’m still learning too, so I’m glad that sharing my real experiences, including the mistakes, has been helpful. Starting young gives you plenty of time to learn how Bitcoin actually works. Stay curious and welcome to the journey. From Türkiye. ⚡
Thank you. That’s a good reminder. I’m learning that Stacker News isn’t only about earning sats it’s also about supporting the people and posts that bring value to the community. I’ll make sure to pass some forward.
Thank you. Your support means a lot to me. I’ll continue sharing my experiences and doing my best to contribute thoughtful, high-quality posts.
That’s encouraging thank you!
I actually received my first 25 real sats in my Blink wallet from this post. So writing about the experiment has already earned me more meaningful bitcoin than the mining experiment itself. 😄
I’ll keep sharing what I build and learn along the way. Reaching the first 10k sats here now feels far more realistic than waiting 8.6 billion years for a block.
Hey stackers,
I’ve been experimenting with CPU mining on the RandomX algorithm and built a custom client called CPU-Miner-Lab-RandomX v3.0 to test things out firsthand.
Lately, I’ve been running tests across various pools and even tried solo mining, which turned out surprisingly effective. The initial benchmarks are looking solid—stable connections, zero rejected shares, and consistent hashrate delivery without unnecessary overhead.
For those actively mining RandomX or building custom setups: what are your go-to practices for optimizing client performance and ensuring smooth pool compatibility? Would love to hear your insights.