Inconvenient truths

When we talk about Bitcoin scalability we inevitably talk about the blockchain trilemma.

The blockchain trilemma is a concept that explains the difficulty of balancing three key properties in a blockchain network: decentralization, security and scalability.

Imagine the vertices of a triangle, it is impossible to change the angles of two vertices without affecting a third and in the same way if you lengthen the vertex of a triangle it also affects the angles of the other two vertices.

Bitcoin prioritizes decentralization and security at the expense of scalability.

Therefore, if or if not, we are going to need alternative solutions to the L1 layer to scale because we want Bitcoin to remain decentralized and secure. This is where the rest of the cryptocurrencies fail, either not accepting the blockchain trilemma or outright lying to users. If Monero were to have mass adoption with its dynamic block size, who would be able to run the nodes? Only the megacorporations like Apple, Microsoft or Amazon. And block size also affects security, the less decentralized a Blockchain is, the more insecure it is.

That said, we have to accept that not everyone will be able to use the L1 layer, Bitcoin does not understand rights, and we will have to accept the trade-offs of scaling solutions.

That said, neither drivechains nor sidechains are feasible scaling solutions in the long term as they are still blockchains.

Lightning is only scalable if we assume losing self-custody. If everyone adopts Lightning and we need one channel per human, it would take decades to open all the necessary channels (about 40 years), the fees would be huge and obviously not everyone could afford to open a channel, it is an oxymoron in itself.

And this brings us to ARK's vUTXO (virtual UTXO) model or statechains like Mercury Layer or Spark. The only way to scale and maintain self-custody, at least so far, will be to use these solutions that do not rely on a blockchain and accepting their trade-offs in terms of security and decentralization.

And for these solutions to be scalable they will have to face the challenge of leaving as small a footprint on the blockchain as possible, and this implies that many people will never be able to go out to the L1 layer.

The other alternative is full reserve Bitcoin banks, and this we know always ends up in a fractional reserve Fiat system. Both Satoshi and Hal were always very clear about these trade-offs in fact Hal himself talked about Bitcoin banks as a way to scale.

In conclusion, we must emphasize that Bitcoin does not understand rights, that Bitcoin has never been scalable, Satoshi and Hal knew it from the beginning, that the trilemma of the blockchain cannot be violated, it is like the laws of thermodynamics and that the only way to deal with scalability are layer 2 or even layer 3 solutions assuming the trade-offs.

We have no alternative to the Fiat system scam other than Bitcoin as it is, the rest are just lies and false pretenses.

BlackBerry was one of the most private devices out there, they even adapted a great architecture like QNX (after its acquisition) in its last years of life and were one of the first if not the first to use point to point encryption in a messaging client.

It was even the standard for many governments, including the genocidal Obama, now the standard is iOS.

The moral is that the best does not always win.

How does everyone feel about the B symbol with the two lines through the outside? Can we live with that as our logo?

WTF. nostr:note1prrxek0w6r8efj4njc3732tgfwv5auzwu6ksmwesr9zce8ysqu5qasqxs8

😂

Jeff both should sell his house and guitars and buy them back later if he’s going around town saying this over and over

I am once again telling you that the only way Nostr wins is for people with big followings committing to walking off the plantation. There is no other way. All other talks of adoption are fruitless. Be the network effect you want to see. nostr:note1levjqr49mm8f3hrfty8s5luspaqa09y3rj0a40p3qyvxgn526tls6mrhht

you need to go study the principles of Unix if you don't understand why having the messages in JSON is better..

the default websockets use Flate compression and this is pretty decent at deduplicating the high entropy pubkeys

if you want to make a relay and client that works with a binary format, go make it, but you will have a bad time if its primary support of JSON is not kept fully up to date, interoperability > all

by obscuring data in a binary format you create all kinds of problems with interoperability, debugging, and so on, i'm not saying don't do it, but it's a low priority compared to fully supporting the easy to debug human readable format, even if json is shitty for certain parts of it syntax it's still readable

here's the principles of unix, summarised by Brave's AI:

-----

Write programs that do one thing and do it well: Focus on simplicity and single-purpose tools.

Write programs to work together: Design tools to be modular and interoperable.

*Write programs to handle text streams: Use text as a universal interface for data exchange and processing.*

Additional Principles

From “The Art of Unix Programming” by Eric S. Raymond:

Rule of Clarity: Clarity is better than cleverness.

Rule of Composition: Design programs to be connected with other programs.

Rule of Separation: Separate policy from mechanism; separate interfaces from engines.

Key Concepts

*Plain text: Store data in plain text files.*

Hierarchical file system: Organize files and directories in a hierarchical structure.

Treat devices and IPC as files: Use a file-like interface for device management and inter-process communication.

Use software tools: Prefer small, specialized programs (tools) over monolithic applications.

Command-line interface: Use a command-line interpreter to string together tools and execute tasks.

Notational Conventions

A small workout is better than no workout. A small stack is better than no stack. Small steps in the right direction are better than no progress.

I’m done with hoping people wake up to Nostr. I like it and they can all fuck off.