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

Bitcoin's layer 2 post thoughts #1

Open
roughpandaz opened this issue Dec 29, 2023 · 0 comments
Open

Bitcoin's layer 2 post thoughts #1

roughpandaz opened this issue Dec 29, 2023 · 0 comments

Comments

@roughpandaz
Copy link

roughpandaz commented Dec 29, 2023

It's great to see ABCDE investing in the BTC ecosystem, and I look forward to seeing you guys do more @bmanlee @hsyodyssey.

Context:

BTC layer 2s do not currently have a clear definition. Lighting, Stacks, Rootstock, Bitmap, and Bsquared are all grouped together, even though they have different security models, values, and impact Bitcoin's ecosystem in various ways (increasing fees vs reducing fees).

Question:

How do you evaluate Bitcoin layer 2s?

Suggestion:

There should be some matrix to define what constitutes a Bitcoin Layer.

  1. Technical alignment: Does the project follow the technical ideas behind Bitcoin (UTXOs, PoW, etc)? Will it help Bitcoin's security in the long term?
  2. Technical Infra: What infrastructure is required to implement this L2. As discussed in Vitalik's recent posts, many "L2s" on ETH run on a single sequencer, have no plans to decentralize their control and can often censor users.
  3. Values alignment: Is the project aligned with the values of Bitcoin? Does it support decentralization? Is it censorship-resistant?
  4. Team alignment: Are the teams aligned with the values of Bitcoin? How are they incentivized?
@roughpandaz roughpandaz changed the title Bitcoin's layer 2 post Bitcoin's layer 2 post thoughts Dec 29, 2023
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

1 participant