It's raining BIPs, hallelujah...
Recently merged:
BIP53
BIP54
BIP172
BIP177
BIP321
BIP443
On the cusp:
BIP77
Maybe a good time to remind that BIPs are author documents that represent the authors’ recommendation to the Bitcoin community.
Login to reply
Replies (54)
Burn BIP177.
BIP-177
Wake up, babe, 3 of these are consensus soft forks and all people will talk about are the 2 about what to name/rename sats.
It's raining BIPs, hallelujah...
Recently merged:
BIP53
BIP54
BIP172
BIP177
BIP321
BIP443
On the cusp:
BIP77
Maybe a good time to remind that BIPs are author documents that represent the authors’ recommendation to the Bitcoin community.
View quoted note →
How about no to all of them?
You didn't even read them
That's the neat part, I don't need to.
I see, just wait for mechanic to go on a podcast to tell you what to think. No need to do it yourself.
No zaps for you? Why not add lightning to your nostr, Murch?
Did you even listen to a Mechanic podcast?
That's like the exact opposite of what he's saying.
BIP177
The point was about what you think, not him
A better idea is just to decide that it's all BS and stop messing with the code. You don't need to read any of them, or listen to anyone's opinion, if that's your position.
If we don't "mess" with the code, it'll eventually stop working. How is that better idea than to continue maintaining and to improve the efficiency of the code? 🤔
Also if somebody finds a way to increase privacy while making transactions smaller, why is it better to not explore and "mess" with it? 🤔
One of them is to fix something that's potentially broken.
My trust in Devs is at an all time low. I thizits better if they just stop touching the code. They have done enough damage already.
Feeling cute. Might write a BIP.
bips are irrelevant now
And how did you arrive at that opinion? Have you talked with any devs?
Doubtful
Highly recommend looking through @Murch 's posts. I don't know about the other devs, but at least he's out here putting in good faith efforts to educate and argue for the core dev's position on things.
Mh, still ob the fence whether to bother with yet another social media platform, so I've put little effort into seeing it up so far
you already have an address, it's <your_npub>@npub.cash
Okay, why's that? Kinda confused why I spent 30% of my work time on the BIPs repo in the past year, if they're relevant now.
Good point. @Murch youre missing out on a pretty cool part of this "social media platform". It's probably easier than setting up your NIP-05
Would that work from amethyst, or do I need to operate the wallet from the website?
I hear there will be two more, soon 👀
That was pretty easy, so that's a good argument.
What I've tried so far, was to set up receiving with Phoenix. I figured a bolt12 invoice might work, or the BIP353 username would, but neither seemed to work from Amethyst when I tried in my own profile. I moved recently and haven't set up my homenode again, so I was considering doing that one of the coming weekends, but maybe I'm missing a way easier way of doing it?
Your lightning address has to be lnurl. As @calle suggested, you could set up the npub.cash address which is custodial and then withdraw your sats from there periodically
Non-custodial is probably not less work than a nip-5, I take it? 😅
Some wallets like @ZEUS or @Alby Hub make self-custody lnurl easier (it's still their domain as the address). Theres also a @npub155m2...dcvg extension.
BIP353 has probably not really arrived yet, has it?
What is the second one? I got BIP77 and I'm drawing a blank for the other. You cooking something? 😉
Correct, unless you ask @Matt Corallo 😅
It's not 77. We hope to get it into the ML in the next two weeks ™
Not arrived in nostr. Starting to arrive everywhere else. Nostr people just like trusted intermediaries 🤷♂️
Tradeoffs have been made while work continues toward sovereign and custodial solutions. I think bolt12 zaps will be a thing at some point.
Been listening to the Bitcpin Optech podcast. Just zapped 69 sats to npub.cash.
Whatcha writin' about?
Alright, gonna keep my eyes peeled. Thanks for going to the ML first, we've been getting a lot of halfbaked stuff first-seen as pull requests lately 😅
I guess I'll have go claim it then.
You can put the LN address in your amythest profile and I think theyll send you DMs when you get zaps so youll know to claim them.
If enough wallets support BOLT12 we may see some progress there, but LNURL works well for most people at the moment. Self-custodial wallets like @ZEUS and Misty @Breez ⚡️ offering a Lightning address help, but if you run your own node, either on a physical machine or in the cloud with @Alby, you get a seamless experience with NWC. It’s worth the effort to set up, IMHO.
Sure, but you can’t even send a zap over some public NWC endpoint, and even if you could you should still prefer BOLT 12 for privacy reasons.
My dude, we’ve been promised BOLT12 is coming real soon for 5 years.
At some point you just have to work with the tools you’ve got.
Huh? BOLT 12 *is* here? It’s been available in all major lighting implementations for several years now (LND via LNDK). It is a tool you’ve got.
It doesn’t matter if the majority of user-friendly wallets don’t use it yet, and Nostr clients don’t have any integration for it.
And to be fair, I’ve tried using it recently to make payments between Phoenix and Misty Breez and had multiple failures.
Someone show me BOLT12 working at scale, please.
We worked with Phoenix and Boltz to improve it, let us know if something isn't working as expected after the latest updates (both Phoenix and Misty).
It takes time to get wallet adoption. We just added full bolt12 in our nodeless SDK this week, we still don't have it on Greenlight. But I agree with Matt, it's here, and we need to push for wider adoption.
Dunno, I’ve never had issues paying or receiving from/to Phoenix, but definitely engage with breez! As for nostr not supporting it yet, well, sounds like a great time for someone to step up and do the work!
if everything is a bip nothing is a bip
also missing bips for all the l2s currently in dev
So, what you're saying is that we have not been selective enough for accepting recent submissions?
It was with too hard to get a BIP processed in the past, and now people put BIPs on a pedestal.
But BIPs are author documents. They don't present community consensus, they're the authors’ personal recommendation to the Bitcoin community, especially in Draft status.
It's good that we get a few controversial BIPs. It helps to make it clear that it's still the readers’ responsibility to make up their mind.
It was with too hard to get a BIP processed in the past, and now people put BIPs on a pedestal.
But BIPs are author documents. They don't present community consensus, they're the authors’ personal recommendation to the Bitcoin community, especially in Draft status.
It's good that we get a few controversial BIPs. It helps to make it clear that it's still the readers’ responsibility to make up their mind.
It was with too hard to get a BIP processed in the past, and now people put BIPs on a pedestal.
But BIPs are author documents. They don't present community consensus, they're the authors’ personal recommendation to the Bitcoin community, especially in Draft status.
It's good that we get a few controversial BIPs. It helps to make it clear that it's still the readers’ responsibility to make up their mind.