Pages:
Author

Topic: (Ordinals) BRC-20 needs to be removed - page 5. (Read 7771 times)

sr. member
Activity: 1190
Merit: 469
Many laptops are still sold with 8 GB nowadays, and from what I've seen, memory stopped following Moore's law in the past 10 years. It's no longer doubling every 18 months, it now takes a lot longer to see "standard" new laptops double in memory.

i'm sure you can buy desktops with even more then 128GB of RAM. but this one can be configured with 128.

https://www.dell.com/en-us/shop/desktop-computers/optiplex-small-form-factor/spd/optiplex-7020-plus-small-ff/gctoo7020sffpus_vp?redirectto=SOC&configurationid=9e300b86-379e-4ddb-8b2c-d9e498e02ccc

there will always be a market for lower end stuff that only has 8GB. that's for people who just want to send some emails and watch a few youtube videos. nothing more...and there's plenty of places that will sell you something like that just realize, you won't be able to do much with it. not as time goes on.

But it's the price you pay to remove the need for trust.  You wouldn't have to do any of it if you were happy to rely on people being honest, but that wouldn't be the trustless and secure network we've built.  We know it's inefficient, but it is vital. 
well yeah i mean bitcoin is definitely inefficient. it uses alot of electricity worldwide. but i dont know of a more efficient way of having a decentralized payment system.

Quote
Plus, some people are offering to do all that for you so that you don't have to.  Maybe show some appreciation by not asking to make their task any more challenging than it already is.   Wink

bitcoin sure is lucky so many people are willing to store the blockchain FOR FREE. and not only store it but let other people use their internet connection to download things from them. and let them send their transactions to them for forwarding to other people. sounds like slavery to me.  Huh


Quote
There are merely practical considerations people need to be aware of.  Idealism has its place, but it works like it does for good reasons and I get the sense that people don't fully appreciate those practical considerations when they ask for changes.
customers are always going to be asking for new services and things. and no they might not always understand underlying issues. like people working for no pay. but that's a problem with bitcoin and how it was designed. i'm not sure we have the right to tell people "no, you can't do that using bitcoin. because i'm running a node and no one is paying me and i don't want to store even more data." customers would not understand why someone would work for no pay. and donate their time and resources. and that's the beginning of being treated with no respect, like a doormat. for people running full nodes...
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
If you happen to own computer with big RAM which can store all UTXO, using HDD should be fine.
I can confirm this, 32 GB RAM and HDD works just fine Smiley

Another point worth mentioning is that spending 2x on your RAM or anything else isn't going to make running your node 2 times faster. Things don't scale this way
If you have enough RAM, you're right. But if your system is short on RAM, doubling the RAM could improve the performance a lot more than just doubling it.

I think 16GB of RAM is plenty right now.
I'd like to have more, but my laptop can't handle it.

It won't be faster, and it won't reduce system load. Besides, if you downloaded one wrong bit in a block, you'll have to start over.
sounds like a nightmare having to run bitcoin core. to be quite honest.
Maybe you should try it. There's a reason Bitcoin Core downloads and verifies blocks at the same time, and it works quite well.
legendary
Activity: 3934
Merit: 3190
Leave no FUD unchallenged
Quote
Downloading isn't resource intensive, verifying all data is what gets you.
yeah that doesn't sound too fun. having to download other peoples' monkeys and not only do that but also verify them too. Shocked just so that you can prune the monkeys later on.

But it's the price you pay to remove the need for trust.  You wouldn't have to do any of it if you were happy to rely on people being honest, but that wouldn't be the trustless and secure network we've built.  We know it's inefficient, but it is vital. 

Plus, some people are offering to do all that for you so that you don't have to.  Maybe show some appreciation by not asking to make their task any more challenging than it already is.   Wink


Quote
It won't be faster, and it won't reduce system load. Besides, if you downloaded one wrong bit in a block, you'll have to start over.
sounds like a nightmare having to run bitcoin core. to be quite honest.

There are merely practical considerations people need to be aware of.  Idealism has its place, but it works like it does for good reasons and I get the sense that people don't fully appreciate those practical considerations when they ask for changes.
sr. member
Activity: 1190
Merit: 469
I have said that I, and all of us, would rather leave Ordinals as they are, than moving them to the UTXO set. I don't think anyone would disagree with this statement. Ordinal users would continue clogging up the network with trash, it's just that this time, we'd have an extra burden to account for; an inflationary UTXO set. Why should we incentivize ourselves towards that direction?

i understand your viewpoint of letting ordinals continue to exist so that people don't try and use something like bitcoin stamps more but if bitcoin is robust, then it shouldn't matter how many people want to use bitcoin for multisignature transactions using bitcoin stamps or any other multisignature software.


A large multisig, done with OP_CHECKMULTISIG is harmful, because it has at least O(n^2) complexity (it can be bigger, if you have a lot of multisig transactions, connected with each other).
so what are you saying exactly, that you wish OP_CHECKMULTISIG was not a part of bitcoin? you do realize it is not going anywhere but i think taproot multisignature is cheaper in terms of fees so people might opt for it instead. to your approval.


You're missing the point. You asked why a large UTXO set is a problem, and your solution is to buy more RAM? So in the same post in which you argued Linux is removing support for systems with 4 MB RAM, you argue 8 GB isn't enough. I'd argue adding more RAM doesn't scale well: what if there are 100 times more UTXOs? Add 2 TB RAM to run Bitcoin Core?

I think 16GB of RAM is plenty right now. In 3 years, you upgrade to 32. 3 more years, upgrade to 64. Does that not sound reasonable because it does to me. Applications are going to increase in their system requirements there's no doubt about that. Thinking you can really get by with 8GB forever is not really realistic in my opinion.

Quote
Downloading isn't resource intensive, verifying all data is what gets you.
yeah that doesn't sound too fun. having to download other peoples' monkeys and not only do that but also verify them too. Shocked just so that you can prune the monkeys later on.

Quote
It won't be faster, and it won't reduce system load. Besides, if you downloaded one wrong bit in a block, you'll have to start over.
sounds like a nightmare having to run bitcoin core. to be quite honest.

legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
The solution to your problem is to get a more poweful CPU and alot more RAM.

This isn't exactly cheap or efficient. Anything that relies on infinite resources is deemed to fail. In fact, if adding more resources were actually a good "fix," then we would never be talking about the UTXO set. The whole idea of the UTXOs set was never a part of the original Bitcoin software. It only came into existence when "adding more RAM" was no longer feasible. The original method of verifying transactions involved searching the entire blockchain, and then we hit a brick wall and had to find a meaningful solution, which was the UTXO set (not more RAM).

The ideal scenario for outputs is to never be stored on your disk. They should be in the memory buffer, then wiped out as soon as they are spent. But because the set has grown too much, we need to flush them to the disk. Obviously, having more of them needing to be in the memory buffer or even on disk makes transaction verification, block reorgs, and everything else more time and resource-consuming.

Quote
I'm still baffled how, and i know this might sound a bit off topic, but how downloading the entire blockchain is apparently some type of CPU/RAM/SSD-HDD intensive process. That makes no sense to me.

Glad you mentioned this; it's another issue with the UTXO set. The set is never downloaded; it gets extracted from the blocks. You need to download the block, verify it, extract the UTXO set from it, and move to the next block. The number of iterations you have to do is going to be similar regardless of which way you decide to sync your node. The more UTXOs, the slower the process. Even if you manage to magically have the entire blockchain copied to your drive in 3 seconds, digging into every block to construct the UTXO set is most certainly going to take forever.

Another point worth mentioning is that spending 2x on your RAM or anything else isn't going to make running your node 2 times faster. Things don't scale this way, and the most important thing you need to remember is that aside from central exchanges, some wallets, and mining pools, everyone else is running their node at a net loss. So why would you want to make life more difficult for those maintaining the ecosystem just so that the Orindals' fools get to protect their useless shit from pruning?"
legendary
Activity: 1512
Merit: 7340
Farewell, Leo
You seem to have suggested previously that ordinals is "good" because it stops people from using something like bitcoin stamps instead.
I have said that I, and all of us, would rather leave Ordinals as they are, than moving them to the UTXO set. I don't think anyone would disagree with this statement. Ordinal users would continue clogging up the network with trash, it's just that this time, we'd have an extra burden to account for; an inflationary UTXO set. Why should we incentivize ourselves towards that direction?

i disagree that something can be judged as good or preferred just because it stops or offers an alternative to something which is a built in feature of bitcoin (multisig) being used in way that you think might be harmful.
If something can't be judged as good or preferred according to you, then why are you arguing that Ordinals should be moved to the UTXO set?
legendary
Activity: 2870
Merit: 7490
Crypto Swap Exchange

You still can use Linux on old or low end machine, assuming you choose light DE (such as XFCE) or distro specially created for such machine.

yes but older hardware and older cpus are becoming deprecated by the linux kernel developers.

Linux Kernel May Drop i486 Support as Torvalds Backs Pentium Plan
https://www.tomshardware.com/news/linux-removes-486-cpu-support

Linux Kernel Nixes IDE Support In the Latest 5.14 Release Candidate
https://www.tomshardware.com/news/linux-kernel-nixes-ide-support-in-the-latest-514-release-candidate

It's far more than older hardware. i486 disconnected on 2007[1], while SATA (as successor of IDE) exist since 2003[2]. Although if you intend to keep using device with i486, consider NetBSD which claim to support i486[3]. Although FYI i386 which also disconnected on 2007[4] still supported by some Linux distro, such as Debian[5].

Quote from: LoyceV
With just 8 GB RAM, Bitcoin Core is pounding my SSD at maximum capacity for hours during IBD. Even though it's just a one-time thing, it's only getting worse.
The solution to your problem is to get a more poweful CPU and alot more RAM. To be quite honest, that's the only solution to your problem. And maybe a faster SSD. Is your SSD NVME or is it SATA? Maybe you need to get an NVME one.

If you happen to own computer with big RAM which can store all UTXO, using HDD should be fine.

[1] https://en.wikipedia.org/wiki/I486
[2] https://en.wikipedia.org/wiki/SATA
[3] https://wiki.netbsd.org/ports/i386/
[4] https://en.wikipedia.org/wiki/I386
[5] https://wiki.debian.org/SupportedArchitectures
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
yes but older hardware and older cpus are becoming deprecated by the linux kernel developers.
You're grasping at straws. Try to find a new Windows version that runs on 35 year old hardware.

so what's the big deal then about the UTXO set getting too bloated?
With just 8 GB RAM, Bitcoin Core is pounding my SSD at maximum capacity for hours during IBD. Even though it's just a one-time thing, it's only getting worse.
(restored quote to include context)
The solution to your problem is to get a more poweful CPU and alot more RAM. To be quite honest, that's the only solution to your problem. And maybe a faster SSD. Is your SSD NVME or is it SATA? Maybe you need to get an NVME one.
You're missing the point. You asked why a large UTXO set is a problem, and your solution is to buy more RAM? So in the same post in which you argued Linux is removing support for systems with 4 MB RAM, you argue 8 GB isn't enough. I'd argue adding more RAM doesn't scale well: what if there are 100 times more UTXOs? Add 2 TB RAM to run Bitcoin Core?

Quote
I'm still baffled how, and i know this might sound a bit off topic, but how downloading the entire blockchain is apparently some type of CPU/RAM/SSD-HDD intensive process. That makes no sense to me.
Downloading isn't resource intensive, verifying all data is what gets you.

Quote
1) download all the raw data
2) once download is complete, then process the data

to me that seems more reasonable than trying to do both things at once.
It won't be faster, and it won't reduce system load. Besides, if you downloaded one wrong bit in a block, you'll have to start over.
copper member
Activity: 821
Merit: 1992
Pawns are the soul of chess
Quote
a built in feature of bitcoin (multisig) being used in way that you think might be harmful
It is harmful. A large multisig, done with OP_CHECKMULTISIG is harmful, because it has at least O(n^2) complexity (it can be bigger, if you have a lot of multisig transactions, connected with each other). To notice that, you can check, how many transaction hashes are computed, how many times is FindAndDelete() called, and how complex it is, to verify 15-of-15 P2SH multisig, or 20-of-20 bare multisig. If you misuse it, then it is possible to create a block, which will take at least a few minutes to verify. And guess what: we have 10 minutes per block! Guess, what will happen, if blocks will be spammed with multisig, and it would take 3 or 5 minutes to verify a single block!

Because if you ever wondered, why sigops limit is there in the first place, then the answer is simple: it prevents that particular attack, related to OP_CHECKMULTISIG.

Edit: https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures#CVE-2013-2292
hero member
Activity: 813
Merit: 1944
Quote
The solution to your problem is to get a more poweful CPU and alot more RAM. To be quite honest, that's the only solution to your problem.
It is not the only solution. For example: if non-interactive transaction joining would be available on the protocol level, then the same number of transactions per second, could be written on-chain, with smaller amount of bytes. Which means, that if you can batch things, then you can have quite small block size, but confirming a lot of transactions. And the same is true, when it comes to data compression: if you compress for example historical address reuse, then it makes Initial Blockchain Download faster.

Quote
but how downloading the entire blockchain is apparently some type of CPU/RAM/SSD-HDD intensive process
Because it is written in a download-and-verify trustless style. If you just select your bitcoin directory, and do copy-paste on your hard drive, it could take minutes, maybe hours, depending on your hardware. However, if you want to get that data from another peer, over the Internet, and make it trustless, and also assume, that some node may be malicious, and serve some invalid data, then guess what: you have to verify it! And that verification is the main bottleneck.

And of course, you can skip verification, if you really want. Many altcoin users shared their bitcoin directory, with already created and verified database. But guess what: in this way, you don't verify, you just trust. And the whole problem of verification time is not related to existing users and nodes, which already know, that the history is correct. It is more related to new nodes, which has to verify everything for the first time, and to some pruned nodes, which may need to re-download and re-verify the chain, if their pruned node will crash for whatever reason (or if there would be any chain reorganization, which is deeper than their pruning point).

Quote
Why not break it into steps:

1) download all the raw data
2) once download is complete, then process the data

to me that seems more reasonable than trying to do both things at once.
Because then, you may waste a lot of resources, if you encounter some malicious node. For example: some ASIC user may want to test "the longest chain rule". It is easy to produce one million blocks with minimal difficulty. Then, if you don't verify anything, you will download a lot of gigabytes, only to notice, that since block 123,456, something is wrong, and there is some heavier chain, which is shorter, but contains a bigger chainwork. And it is not only about that, there are many attacks, where something could go wrong, and where you may end up downloading a lot of data from some peer, to conclude in the end, that the whole chain is invalid since block number N. Another example: sigops limit per block. Even some mining pools sometimes get it wrong: https://bitcointalksearch.org/topic/error-connectblock-too-many-sigops-invalidchainfound-invalid-block-5447129
sr. member
Activity: 1190
Merit: 469

You still can use Linux on old or low end machine, assuming you choose light DE (such as XFCE) or distro specially created for such machine.

yes but older hardware and older cpus are becoming deprecated by the linux kernel developers.

Linux Kernel May Drop i486 Support as Torvalds Backs Pentium Plan
https://www.tomshardware.com/news/linux-removes-486-cpu-support

Linux Kernel Nixes IDE Support In the Latest 5.14 Release Candidate
https://www.tomshardware.com/news/linux-kernel-nixes-ide-support-in-the-latest-514-release-candidate


Quote from: LoyceV
With just 8 GB RAM, Bitcoin Core is pounding my SSD at maximum capacity for hours during IBD. Even though it's just a one-time thing, it's only getting worse.

The solution to your problem is to get a more poweful CPU and alot more RAM. To be quite honest, that's the only solution to your problem. And maybe a faster SSD. Is your SSD NVME or is it SATA? Maybe you need to get an NVME one.

I'm still baffled how, and i know this might sound a bit off topic, but how downloading the entire blockchain is apparently some type of CPU/RAM/SSD-HDD intensive process. That makes no sense to me. I can download things and it's not CPU or RAM intensive at all. Maybe bitcoin has a problem where it is trying to do too many things at once. Why not break it into steps:

1) download all the raw data
2) once download is complete, then process the data

to me that seems more reasonable than trying to do both things at once.


Quote from: BlackHatCoiner
In which Universe have I argued the opposite?
You seem to have suggested previously that ordinals is "good" because it stops people from using something like bitcoin stamps instead. i disagree that something can be judged as good or preferred just because it stops or offers an alternative to something which is a built in feature of bitcoin (multisig) being used in way that you think might be harmful. we don't even know that people would adopt that alternative if "ordinals" didn't even exist.
legendary
Activity: 1512
Merit: 7340
Farewell, Leo
because they don't care about data permanence. these people are uninformed, and don't understand the difference between something like bitcoin stamps which stores data directly into the utxo set which can never be pruned vs ordinals data which can be pruned.
So what if the Ordinals' data can be pruned? Full nodes must keep track of everything, otherwise new nodes can't sync up.

they're not getting what they're paying for though in my opinion.
Your opinion on whether it's worth to pay for an Ordinal is irrelevant in a decentralized network, no offense. The market decides if it's worth it or not.

all the people running nodes and things are just laughing saying "i'll just prune your data". do you think that's really fair? 
This can't happen. If all nodes prune that data, there can never be any new nodes. The "actual users" side is definitely losing more than it is gaining.

whats so difficult for you to understand that a multi-signature bitcoin transaction is none of your business unless you are a party to it.
In which Universe have I argued the opposite?
legendary
Activity: 2870
Merit: 7490
Crypto Swap Exchange
I get your point, although it makes sending Bitcoin become less convenient.
yes, but at the same time, it prioritizes "important" transactions. i don't really consider a transaction important if one of the parties is not even willing to do anything.

That makes sense, although i disagree what counts as "important" transaction.

that could cut down on spam transactions like address poisoning. i'm assuming you've heard about that scam. and other types of dust spam which no one wants.

It's probably true since malware needs to replace both real address and signature. Although dedicated scammer wouldn't have hard time adapt to change.

about the utxo set being 11GB now. it very well could be. i had just googled what its size is and say 4GB.

It very well could be? It's a fact (at least if you use Bitcoin Core). I'd recommend you to check https://statoshi.info/d/000000009/unspent-transaction-output-set?orgId=1&refresh=5s&from=now-5y&to=now which shows some stats about UTXO.

but the situation reminds me of how Linux used to be for low end machines that had limited resources like a slow cpu, small hdd, low amount of ram. if you want to really run linux now, you need a much more modern machine. the same thing is happening with bitcoin as far as being able to run a node. linux is not for geeks with no money who cobbled together some old hardware. those days are long gone. off my soapbox about that now!

Not very good comparison though. You still can use Linux on old or low end machine, assuming you choose light DE (such as XFCE) or distro specially created for such machine.
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
so what's the big deal then about the UTXO set getting too bloated?
This:
During the last hours, sync speed was limited by my SSD speed (and the lack of RAM).
With just 8 GB RAM, Bitcoin Core is pounding my SSD at maximum capacity for hours during IBD. Even though it's just a one-time thing, it's only getting worse.
sr. member
Activity: 1190
Merit: 469
Why do you think they won't be willing to put it into the UTXO set?
because they don't care about data permanence. these people are uninformed, and don't understand the difference between something like bitcoin stamps which stores data directly into the utxo set which can never be pruned vs ordinals data which can be pruned.


I get your point, although it makes sending Bitcoin become less convenient.

yes, but at the same time, it prioritizes "important" transactions. i don't really consider a transaction important if one of the parties is not even willing to do anything. that could cut down on spam transactions like address poisoning. i'm assuming you've heard about that scam. and other types of dust spam which no one wants.

about the utxo set being 11GB now. it very well could be. i had just googled what its size is and say 4GB. but the situation reminds me of how Linux used to be for low end machines that had limited resources like a slow cpu, small hdd, low amount of ram. if you want to really run linux now, you need a much more modern machine. the same thing is happening with bitcoin as far as being able to run a node. linux is not for geeks with no money who cobbled together some old hardware. those days are long gone. off my soapbox about that now!


I don't get all the subterfuge.  Why aren't people honest about their intentions?  Just get straight to the point and admit that you want a centrally planned economy where you can redistribute wealth as you see fit. 

what i think about "redistributing wealth" has nothing to do with what i was saying about solving the UTXO set bloat issue. or my remarks about what i thought was causing it. sorry you think i'm trying to redistribute your bitcoin to other people because i'm not.

Quote from: LoyceV
I don't really mind UTXOs, as long as they don't need to be in memory. Who cares about a few GB more storage on disk, as long as it doesn't need to be in RAM or read from disk all the time?
hmmm I've never heard anybody say that before.

Quote
I guess it's less inefficient than I thought. If "inactive" UTXOs are just left untouched by Bitcoin Core, fine by me.
so what's the big deal then about the UTXO set getting too bloated? you're running a full node and you don't have any problem with the UTXO set so maybe there isn't one. and people are being irrational in thinking that that if monkeys didn't live in ordinals but swung over to bitcoin stamps it would destroy bitcoin...

legendary
Activity: 2870
Merit: 7490
Crypto Swap Exchange

It's also worth to mention higher total UTXO also require either more RAM or slower verification time (since you need to read the data from disk). It's especially slow during IBD process if you don't have enough RAM to store all UTXO on it.
the utxo set is only about 4GB apparently. Mozilla Firefox can eat up 1GB of RAM by itself maybe even more! So I mean, at some point people just have to bite the bullet and upgrade their computer. Because a new computer should be having 32GB of RAM at this point. If not you're getting the wrong computer! Also it might be time to upgrade from a hdd to an ssd because i heard they are alot faster. So maybe you could just store the utxo set on the ssd and not in ram.

yes unfortunately, bitcoin like everything else grows with time and will demand more from the people who want to participate in it (run a full node)...

4GB? I think you saw very old stats. On my device, it's about 11.5GB for mainnet and about 9GB for testnet. And while i agree people ideally should upgrade their computer periodically, i think only Bitcoin enthusiast would upgrade their computer with primary goal to run Bitcoin full node smoothly. And as reminder, renting VPS with big RAM isn't exactly cheap.

Quote
You're expecting receiver signature?
I was just saying that's a possible way to make sure that you don't have non-spendable transactions where the private key to the receiver's public key is not known. aka burn addresses. there's no point for utxos like that to be in the utxo set, is there?

I get your point, although it makes sending Bitcoin become less convenient.
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
First someone proposes "fixing" spam and before long they're talking about "fixing" immutability itself.
I don't really mind UTXOs, as long as they don't need to be in memory. Who cares about a few GB more storage on disk, as long as it doesn't need to be in RAM or read from disk all the time? I just checked my chainstate:
1 .ldb file has date May 6.
1 .ldb file has date May 7.
5924 .ldb files have date May 8.
21 .ldb files have date May 9.
There are no newer files.

I closed Bitcoin Core. Now:
1 .ldb file has date May 6.
1 .ldb file has date May 7.
5923 .ldb files have date May 8.
20 .ldb files have date May 9.
0 .ldb files have date May 10.
11 .ldb files have date May 11.
I use dbcache=1024

I guess it's less inefficient than I thought. If "inactive" UTXOs are just left untouched by Bitcoin Core, fine by me.
legendary
Activity: 1512
Merit: 7340
Farewell, Leo
i want them to make standard transactions so that they cannot be differentiated from any other ordinary transaction that is an actual transaction. so it needs to be in the utxo set. if they're not willing to put it into the utxo set then i'm not really a fan of them storing any type of data
Why do you think they won't be willing to put it into the UTXO set? What's the reasoning here? Aren't they evidently willing to throw millions in the bucket for their crap?

The situation is really simple, yet we've made it unnecessarily complicated. Users can inject arbitrary data whether you like it or not. They can do it either by inflating the UTXO set, or by merely touching it. At the moment, these users don't harm the set by creating an output for every 256-bit chunk their Ordinals weigh, which could be their last resort, again. If you invalidate this "less harmful solution", or make it non-standard, you're pushing them to do the most harmful for the rest of us solution.

What's so difficult to understand?
legendary
Activity: 3934
Merit: 3190
Leave no FUD unchallenged
Not only are "spam" UTXOs a problematic issue with bitcoin but you also have these too:

1) UTXOs that cannot be spent because they are "burn addresses"
2) UTXOs that are no longer spendable because the owner lost their private key (the guy whos hard drive is in a landfill)
3) UTXOs that are very old and it is not clear if they will ever be spent or not (satoshi's bitcoin)

See, this is how it starts.  First someone proposes "fixing" spam and before long they're talking about "fixing" immutability itself.

I don't get all the subterfuge.  Why aren't people honest about their intentions?  Just get straight to the point and admit that you want a centrally planned economy where you can redistribute wealth as you see fit. 
sr. member
Activity: 1190
Merit: 469
NATURAL growth is expected and it is fine, the problem is the artificial growth that is happening due to spam. It's one thing to say UTXOs are people's funds locked up, it's another thing to say a considerable percentage of the UTXO set is the outputs of prolonged spam attacks.

Not only are "spam" UTXOs a problematic issue with bitcoin but you also have these too:

1) UTXOs that cannot be spent because they are "burn addresses"
2) UTXOs that are no longer spendable because the owner lost their private key (the guy whos hard drive is in a landfill)
3) UTXOs that are very old and it is not clear if they will ever be spent or not (satoshi's bitcoin)

It's inefficient to have to store all of these type of things. FOREVER. For who? No one is ever going to use them. At least as far as #1 and #2 are concerned.

Quote from: LoyceV
What really worries me now is that there are barely any normal real Bitcoin transactions left. Mempool Goggles (https://mempool.space/) shows more than 90% of the blocks are filled with "data" (AKA spam). That leaves at most a few dozen "normal" Bitcoin transactions per minute. Bitcoin's transaction rate has always been limited around 7 tps, but currently real transactions barely make it to half a transaction per second. And some of the non-data Bitcoin transactions are like this (https://mempool.space/tx/708c4f6a91cd461c81966c956121f3c9dae135b6bd68be74b681a8608c964b4d): 3 dust inputs plus one normal input > 5 dust outputs plus 2 normal outputs. This is not the "adoption" I hoped for.

whatever is going on there is definitely not what satoshi intended in his whitepaper, in my opinion!  Shocked
Pages:
Jump to: