Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename to sparks? #3

Open
t-bast opened this issue Nov 4, 2021 · 9 comments
Open

Rename to sparks? #3

t-bast opened this issue Nov 4, 2021 · 9 comments

Comments

@t-bast
Copy link
Contributor

t-bast commented Nov 4, 2021

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 👍 (to rename to sparks) or 👎 (to keep blips)

@Bosch-0
Copy link

Bosch-0 commented Feb 17, 2022

Much better name <3

@cryptagoras
Copy link

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)

@t-bast
Copy link
Contributor Author

t-bast commented Feb 21, 2022

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.

@TheBlueMatt
Copy link
Contributor

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.

@t-bast
Copy link
Contributor Author

t-bast commented Feb 22, 2022

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?

@cryptagoras
Copy link

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 😄

@TheBlueMatt
Copy link
Contributor

TheBlueMatt commented Feb 22, 2022

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.

@cryptagoras
Copy link

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 🤐

@jb55
Copy link

jb55 commented Oct 14, 2022

yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants