Not exactly a lie though...

With rollups you can store more transactions per byte of on chain storage.

That said it opens the flood gates for everyone to spam, and it is inexcusable.

Yeah we get it: you're incapable of understanding complex nuanced engineering issues and resort to simpler conspiracy theories that make sense to you. Consider that some Bitcoin implementations don't even have the concept of a separate UTXO set data structure... as Erik Voskuil recently explained:

Libbitcoin is a set of libraries, libbitcoin-database being one of 4 that make up node (system, network, database, and node). (libbitcoin-server is an additional library that adds comprehensive set of client-server interfaces, making the node useful.) libbitcoin-database is an implementation of a simple query interface (defined as a c++ class) over a backing store. The store is a templated collection of tables. The tables are mmap-based head and body files used to construct multimaps, hashmaps, arraymaps, arrays, and blobs. We mock the tables using std::vector, mock the store using the the mocked tables, and test most of the query interface using the mock store. The structure is highly relational, and surrogate keys are exposed to the caller for optimized navigation.

This is an isolated and clear storage abstraction layer. All validation is performed within the chain:: classes (e.g. block, header, tx, input, script, etc.) defined in the base level libbitcoin-system. There is no validator coupling to the store. The store retains chain objects, indexes, and validation state for headers/blocks and txs as they progress through a state machine. There is no utxo table, just natural relations between objects, indexed and related. Validation correctness of course requires store fidelity, but is totally decoupled from it. We validate blocks concurrently, queueing up 50,000 blocks at a time by default (e.g. with 50k threads we would validate all at the same time).

The store could be replaced with no impact to the query interface (as we already do in testing). So it's not really accurate to imply that libbitcoin's validation is tied to mmap or even append-only. Pruning could be implemented in the existing model for example. The existing store could be replaced with something simple and light like SQLite, or a full RDBMS. We had some interns working the SQLite approach last summer. That would be more specialized for low performance scenarios, where the custom database targets ultra high performance.

With sufficient RAM there is never SSD access. The store can sync up and just live in RAM, never touching a disk. Since it is append only, it's very low impact on SSDs. As the store builds, no table body byte is ever re-written. Table heads are hashmaps buckets, small and dynamic. It performs live automated/manual snapshotting, automatic fault detection/recovery on restart, automated disk-full pause/restart, and supports hot backup. Query performance is phenomenal. A warm node can query the full 5.2 million output Electrum query (very complex relations) in 15 seconds on my 2.1GHz workstation. But at the low end, an off-the-shelf store is sufficient. A clear interface and swappable store makes a lot of sense.

A large utxo set makes no difference in this design. There are no operational problems associated with it. This is not theoretical, at this point we are only working on server (client-server interfaces). The utxo set size is a complete non-issue.

Yeah we get it: you're incapable of understanding complex nuanced engineering issues and resort to simpler conspiracy theories that make sense to you. Consider that some Bitcoin implementations don't even have the concept of a separate UTXO set data structure... as Erik Voskuil recently explained:

Libbitcoin is a set of libraries, libbitcoin-database being one of 4 that make up node (system, network, database, and node). (libbitcoin-server is an additional library that adds comprehensive set of client-server interfaces, making the node useful.) libbitcoin-database is an implementation of a simple query interface (defined as a c++ class) over a backing store. The store is a templated collection of tables. The tables are mmap-based head and body files used to construct multimaps, hashmaps, arraymaps, arrays, and blobs. We mock the tables using std::vector, mock the store using the the mocked tables, and test most of the query interface using the mock store. The structure is highly relational, and surrogate keys are exposed to the caller for optimized navigation.

This is an isolated and clear storage abstraction layer. All validation is performed within the chain:: classes (e.g. block, header, tx, input, script, etc.) defined in the base level libbitcoin-system. There is no validator coupling to the store. The store retains chain objects, indexes, and validation state for headers/blocks and txs as they progress through a state machine. There is no utxo table, just natural relations between objects, indexed and related. Validation correctness of course requires store fidelity, but is totally decoupled from it. We validate blocks concurrently, queueing up 50,000 blocks at a time by default (e.g. with 50k threads we would validate all at the same time).

The store could be replaced with no impact to the query interface (as we already do in testing). So it's not really accurate to imply that libbitcoin's validation is tied to mmap or even append-only. Pruning could be implemented in the existing model for example. The existing store could be replaced with something simple and light like SQLite, or a full RDBMS. We had some interns working the SQLite approach last summer. That would be more specialized for low performance scenarios, where the custom database targets ultra high performance.

With sufficient RAM there is never SSD access. The store can sync up and just live in RAM, never touching a disk. Since it is append only, it's very low impact on SSDs. As the store builds, no table body byte is ever re-written. Table heads are hashmaps buckets, small and dynamic. It performs live automated/manual snapshotting, automatic fault detection/recovery on restart, automated disk-full pause/restart, and supports hot backup. Query performance is phenomenal. A warm node can query the full 5.2 million output Electrum query (very complex relations) in 15 seconds on my 2.1GHz workstation. But at the low end, an off-the-shelf store is sufficient. A clear interface and swappable store makes a lot of sense.

A large utxo set makes no difference in this design. There are no operational problems associated with it. This is not theoretical, at this point we are only working on server (client-server interfaces). The utxo set size is a complete non-issue.

Have fun with your "truth" then. Don't come crying later. Everyone interested can read our past discussions and make up his own mind. You anyways will never change without being punched by reality, so you'll deserve what's coming. I just hope you will use it as an opportunity to grow.

many CORETARDS are FIAT-BRAINED fiat lovers.

and even those who say they hate USD still think entirely in fiat. they just view bitcoin through that same BROKEN lens.

I didn't expect arguments, we already discussed and you weren't able to comprehend any it seems. :/

Man why do you spend your time responding to these people (if not LLMs)?

I mean. Sure. But this isn’t exactly Singapore. It’s the epicenter of the largest refugee crisis in the world, totally wrecked by hyperinflation, etc etc

I mean. Sure. But this isn’t exactly Singapore. It’s the epicenter of the largest refugee crisis in the world, totally wrecked by hyperinflation, etc etc

I mean, yes I hope that all dictators fall and that tyranny ceases to exist. This goes for Venezuela and the entire planet

You want a regime change, you want Maduro removed and you want to "support them in their struggle".

Who ever said anything about imposing my will? Where did I ever say that?

The last election was blatantly rigged by the regime

If you believed in them having “sovereignty” you would support them in their struggle

But I don’t think this is what you believe

Trying to twist your wording from the previous note?

You can criticize anyone all day long. Its called free speech.

You can't chose their fate. You can't choose for them. Capisce?

Somebody has to

Nonsense. You should criticize tyrants anywhere and everywhere

no, fool.

Betteridge's Law of Headlines states that any headline ending in a question mark can be answered with "no." This suggests that if a publisher were confident in a positive answer, they would have stated it as a fact rather than posing it as a question.

Today's btc is soooo not the bitcoin satoshi created. The influencers are lying to you!

It's gonna be fun watching you fork off to a network that's only supported by the tiny portion of deranged puritans occupying the echo chamber you've built. 😏

Dude it’s pretty simple

You could say:

I am against US regime change in VZ

I also think Maduro is a brutal dictator who has no right to rule Venezuela

Very easy!

Clint Eastwood is 95 years old and still drives his 1988 car, even though he could buy an entire automobile factory if he wanted.

This photo captures him pumping his own gas, a testament to his grounded nature.

He hasn’t let global fame and wealth change him. In my opinion, that's a true mark of a remarkable person!

You saying he whines like a little girl just shows you’re a sexist. Everything said before that means nothing to me. Even if you’re right.

I just looked at this evidence you submitted to us here in the court of Nostr sir 😀

Your hyperbole doesn’t match what she actually said. Plus there’s at least one edit so there’s that, but still. This is not a crazy evil person talking crazy shit here sorry ya gotta do better to convince me at least….

have fun getting rekt don't forget to wager everything you got on the futures market i'm sure you can tip the scales!

Bitaxe 💯

DATUM 👍

Knots 👎

BIP444 😬

Good luck with that soft fork bro. Remember to dump your legacy coins ASAP or you're just LARPing.

You are utterly fucking delusional, and have entrenched yourself so deeply in your self-delusion that was passed on from your surrounding of and BY other deluded fucks that no level of information provided against it can (or will) sway you.

Hopefully others realize how fruitless it is to "debate" you; insert Mark Twain quote about stupid people here.

GM.

Crazy to think Peter is a Bitcoin Dev and not Ethereum with "usecases". Shocking.

interesting to call someone a cunt when don't even know them. why don't you say it to my face?

interesting to call someone a cunt when don't even know them. why don't you say it to my face?

interesting to call someone a cunt when don't even know them. why don't you say it to my face?

This cycle is going to continue punishing shitcoiners real hard