pull down to refresh
323 sats \ 4 replies \ @endothermicdev 23h \ on: BOLT 11 - Is `n` mandatory or not? lightning
This piqued my curiosity so I hand decoded a bolt11 to check - it had s, p, d, x, c, r, and 9 tagged fields. I guess n is not typically included because you can calculate the public key from the message (bolt11) along with the signature. Omitting it saves space.
Of the tagged fields, only d or h should be included (a description or a hash of the description if it's too long to fit.) p and s are required for payment hash and payment secret, but n is optional. Those still have a mandatory length (even though they have a length field in the invoice) otherwise the reader wouldn't know what to do with them and shouldn't proceed. Keeping these fields with a data length parameter leaves some flexibility for future spec changes I suppose.
That's my interpretation as well.
me too 👀
Obsidian not being open source was one of the reasons I didn’t even start using it, haha
(But not necessarily a good reason, since I did use other closed-source software, like NVIDIA drivers.)
122 sats \ 1 reply \ @endothermicdev 22h \ parent \ on: BOLT 11 - Is `n` mandatory or not? lightning
It's really just this line that's confusing, right? Because
n isn't really mandatory.A reader:
- MUST fail the payment if any mandatory field (
p,h,s,n) does not have the correct length (52, 52, 52, 53).
Because later it's more clear with:
A reader: ...
- if a valid
nfield is provided:- MUST use the
nfield to validate the signature instead of performing public-key recovery.- If the signature is not compliant with the low-S standard rule<sup>low-S</sup>:
- MUST fail the payment
If it confused you, I'm sure it's confused others. I think it's worthwhile to fix unclear wording in the spec.
Evening stackers, gave out my Square Bitcoin pamphlet to a local organic pizza shop this evening. Feels good to take action.
You're right, but that's such a preposterous utopian fantasy.
Scarcity is a fundamental of reality because human wants are unbounded.
I think he's got the OG standpoint wrong. I don't recall many people from early days ever talking about gold standards, not even the e-gold people. That narrative came later. It has to me (and most people around me) mostly been about not being censored and not being tricked; NgU isn't a must-have.
I might have disagreed before. I think I have come around to one page docs though - they’re easier to search and not that much harder to read. Though they need some decent structure
There's not a single mindset of course. This old thread gives some insight of what bitcoiners thought in 2011. There's some sound money / deflationary reasoning, but the majority isn't.
Can we see downzaps the same way we see zaps at some point? Something like this?
Seeing the amount of sats near the post/comment is not accurate anymore, I suggest showing only the total amount of sats+ccs, both upzapped and downzapped.
What would be the issue in showing downzaps? WOuld this make the
outlawed tag irrelevant?We, as stackers, could decide to hide posts by
x unzaps same way we currently do with min amount of sats.Newbies could have a preset amount of
y by default, but in control to change it if desired.I believe slashing needless bureaucratic hoops is something this administration is attempting.
Personally, I prefer a maximally hamstrung state.
I think the "safe" signup process is:
NOTE: Do not use their VPN service or your real IP at any time, also not during signup. Instead use mullvad (obscura perhaps even better). Now they cannot report your IP address.
- Open free account
- Do NOT give them a fallback email
- Once you have the free account, upgrade with bitcoin, pay through submarine swap
@didiplaywell, check it out, a positive piece about Argentina!
Also, export taxes? smh
I think bitcoin self custody is pretty easy already. I think a better way to put the question is how to make secure self custody easier in a way that mitigates against catastrophic risk (i.e. a single point of failure leading to your entire stack being drained)
getting ready for teaching next semester. refactoring my course design. about as annoying as refactoring code
Now we have a place to share our needs, and in the worst case, SN vending machine is open 24/7.
21 sats \ 0 replies \ @Public_N_M_E OP 5h \ parent \ on: Daily Discussion Thread ~Music Saloon! Music
Awesome song. I don't think I've heard this one before.