blips icon indicating copy to clipboard operation
blips copied to clipboard

Rename to sparks?

Open t-bast opened this issue 3 years ago • 9 comments

Now that the spec is called lightning/bolts, I'd find it really cool if this repo was lightning/sparks. It could stand for "SPecifications for Additional Really Kool Stuff/Software".

Please vote on this issue with a :+1: (to rename to sparks) or :-1: (to keep blips)

t-bast avatar Nov 04 '21 08:11 t-bast

Much better name <3

Bosch-0 avatar Feb 17 '22 08:02 Bosch-0

I'm not good at physics but don't sparks come before bolts? So in that metaphorical line of thinking with a blast happening after the bolt, it may be more fitting to have: lightning/blasts with

Bitcoin Lightning Advancement Specs & Transcripts

or something better.

(Advancement|Application|Applied)

cryptagoras avatar Feb 21 '22 12:02 cryptagoras

My line of thinking with sparks is that it's a tiny start of a lightning bolt, which is what we describe here: much smaller things than bolts, that could potentially evolve later into a bolt (it remains to be seen if that "upgrade" path makes sense and is ever used).

I don't like blast, which sounds "bigger" than bolts, which would give the wrong idea about what we're doing here IMHO.

t-bast avatar Feb 21 '22 13:02 t-bast

I feel like the "are bLIPs a pre-BOLT, or something different (ie just a vendor standard)" question is the question here, and I'm not a fan of renaming to imply one or the other yet.

TheBlueMatt avatar Feb 22 '22 00:02 TheBlueMatt

Not necessarily, I quite like spark mostly because it's smaller than bolts, a small addition to the ecosystem (and dislike blast because it's bigger), regardless of whether it may or may not become a bolt afterwards?

t-bast avatar Feb 22 '22 08:02 t-bast

Hmm, I can be wrong but from what I understand bLIPs are about 2 things: i) optional BOLT-like features that could potentially graduate to proper BOLTs if they prove their worth, and ii) application design docs that utilize one or multiple BOLTs/bLIPs. So they can be both on the same level like BOLTs (but optional), and on a higher/application level as well.

Unless I misunderstood and this is strictly for potential BOLT-candidates which certainly would be a more focused approach, however there's already bLIP 10 which is mostly on the app-side.

Btw, the only real plus of blasts is that it contains the letter B to include bitcoin :smile:

cryptagoras avatar Feb 22 '22 10:02 cryptagoras

Not necessarily, I quite like spark mostly because it's smaller than bolts, a small addition to the ecosystem (and dislike blast because it's bigger), regardless of whether it may or may not become a bolt afterwards?

Fair enough. I dunno that I care too much about names, or, really, at all. Y'all do what you want :)

Hmm, I can be wrong but from what I understand bLIPs are about 2 things:

I think it depends a lot on who you ask. Based on text in bLIP 1 today, bLIPs are exclusively about (ii) with maybe an exception for things that weren't intended to become BOLTs but which found their way into everything and maybe then could be BOLTs, not things seeking to eventually become BOLTs.

TheBlueMatt avatar Feb 22 '22 14:02 TheBlueMatt

I see, yeap, I initially got (i) from Ryan's bLIPs intro/proposal on lightning-dev ML, although I didn't translate it precisely. Naming aside, it's pretty certain that (i) apps bLIPs will be the ruling category since the lower bar, so it's not much of an issue.

Anyhow, I don't mind about the name, as much as having a fully capitalized word... that lowercase b is OCD-inducing :zipper_mouth_face:

cryptagoras avatar Feb 22 '22 20:02 cryptagoras

yes

jb55 avatar Oct 14 '22 16:10 jb55