We don’t! That was just one person who deposited a large amount and locked it. This is a bitcoin piggy bank that can be used in many ways, including as a custodial Lightning wallet…

We appreciate constructive criticism, the line between hate and love is thin. Unfortunately, this isn’t about you. And just a heads-up: what you’re doing isn’t activism (you may think it is), you’re just very angry, and that kind of anger hurts you. Sorry!

On the other hand, we’ve built a great product the Bitcoin community hasn’t seen in a long time. It just needs time to sink in, it’s new, and not everyone will get it right away. Good luck.

Fair point on timelocked addresses, but a quick reality check:

A timelock (CLTV/CSV) only enforces time, you can’t do “unlock when price > X” in Bitcoin script without introducing an external oracle (e.g., via DLCs). That brings liveness/trust assumptions, if the oracle is down, wrong, or censored, you may be stuck until a fallback (if any) activates. And in @chebibu’s case the price condition seems central: not everyone wants to die with their BTC unspent, and many have a target price at which they’d sell. That’s exactly the limitation, pure timelocks can’t encode market-driven conditions natively, you either accept oracle risk/complexity or choose a different strategy.

Even if you have the skills to build a safe timelocked address, self-custody introduces different risks: mis-setting the lock time (height vs. timestamp), wallet/tooling quirks, the seed being stolen physically or, if you use a passphrase, forgotten passwords (both of which have happened to people I personally know), device failure, etc. It’s not plug-and-play and definitely not suited to people who haven’t done it before.

On JoinMarket: yes, the fidelity-bonded coins can stay locked/cold, but the maker coins live in a hot wallet. Those are the funds exposed to operational and malware risk. Yield isn’t guaranteed and may not compensate for that risk for everyone.

We’re a new service and haven’t earned your trust or reputation yet. We’ve spent the last 2 years and countless BTC building and hardening this, but we know trust is earned over time. We also believe a large share of the 8B people in the world won’t, or can’t, self-custody at scale for many reasons (operational complexity, recovery challenges, and hard limits like block space). Our aim is to responsibly serve that segment while still respecting and supporting advanced self-custody users.

So you’re suggesting he put his coin into the command prompt terminal?

Adorable tantrum, run along, adults are building.

So you’re the one who decides how people use open, permissionless tech?

Tell me you don’t understand anything about development without saying it directly. Why do you have such a wrong assumption? We’ve been building digital products for 20 years, 10 of those in Bitcoin development.

If you like custodial “trust me bro” coinos.io, you’ll like pig.gy too! Just give it a try! Maybe even change the Lightning address in your profile to your new Piggy 🐽

The business model is selling a unique Piggy, a digital Bitcoin piggy bank, similar to how you might buy a ceramic one for coins.

BTW, the treasury is separate from users’ funds. The treasury is Piggy’s own stash, which will be used for future initiatives.

You probably don’t see the tokenized future yet, bookmark this and re-read in 10 years 🐽

You mean ordinals the tech or ordinals the scummy JPGs? because the tech is just a container, blockchains give public scarcity and composability. if the token actually gates something scarce (payments, seats, licenses, doors, custody, governance), it’s useful. if not, it’s just a picture with a price tag. the value is whatever the key opens, not the jpeg.

ok guys, I’ve gotta jump in. “Not your keys, not your bitcoin” is a great warning, but as a universal mandate it ignores reality: • On-chain capacity isn’t infinite. If every human self-custodied and settled routinely on L1, fees would price out the majority. Global daily commerce can’t live on a scarce settlement layer. • Most people aren’t opsec pros. Seed phrases get lost, mishandled, or stolen. For a lot of users, pure self-custody turns financial risk into personal security risk. • Recovery & inheritance are hard. One mistake, one house fire, one memory lapse, and it’s gone. That brittleness doesn’t scale to billions. • There’s a custody spectrum, not a binary. Multisig with trusted guardians, community/mini-custodians, hardware + social recovery, and regulated custodians with real audits and proof-of-reserves, these are pragmatic middle paths. • Payments vs settlement. L1 should be for final settlement and high-value moves, everyday transactions belong on layers/rails designed for throughput.

Yes, bad custodians have blown up. The answer isn’t forcing grandma to be her own cold-storage CISO… it’s credible, transparent custody options plus easy exit ramps to self-custody when users want it.

So no, on-chain capacity alone isn’t enough for everyone to self-custody and transact. Treat “not your keys” as a north star and safety slogan, not a one-size-fits-all policy.

We have full-blown Nostr integration in our plans!

Totally fair, and great question: Newcomers & gift-givers (gifting or onboarding friends and family), goal-based savers, creators & small communities (accept lightning tips and run quick crowdfunds without heavy setup). You can even use the free version of Piggy as a disposable lightning wallet.

Yep, you can still do that when fees are low, but it’s not as cool as sending an AI Piggy Bank, with easy-to-understand instructions, one-click claim. Also, on-chain Bitcoin will increasingly be used only for high-value transactions.