Bitcoin Forum
December 25, 2025, 07:22:51 PM *
News: Latest Bitcoin Core release: 30.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2]  All
  Print  
Author Topic: Why Bitcoin 30 will probably not lead to more spam in the blockchain (ELI5)  (Read 619 times)
d5000 (OP)
Legendary
*
Offline Offline

Activity: 4508
Merit: 10037


Decentralization Maximalist


View Profile
December 23, 2025, 06:07:12 AM
 #21

Is that your alt account you're talking to, Pepe? Grin Thanks for bumping my thread anyway for free Smiley

(Seriously, do you think swearing will make your arguments look more intelligent? I'm quite curious about the fundaments of this theory.)

Just some reaction because some uninformed people could think you are bringing some kind of argument on the table:

And people like OP claiming a filter doesn't work because it's slowing down the block propagation speed of a block that is full of spam. Completely ommitting that this is precisely the point of the filters: causing trouble to miners who add spam to their blocks.
Erm, it doesn't seem you have understood the compact block mechanism.

The trouble is actually caused to nodes who have too strict datacarriersize configurations, as these have to re-download the transactions they previously "filtered" and then rejected, causing them higher bandwidth costs. Miners? Are fine with Knots and other nodes with different configurations.

Admit that you don't care about nodes at all. Smiley

The world wide demand for cheap forever data storage is infinite.
I don't believe Bitcoin is particularly cheap as a data storage. Even if you add the "forever" word and limit yourself to blockchains which may be able to compete with paper for longevity. Solana, BSV, and other chains are much cheaper. And judging by the fact that even minuscule altcoins from 10 years ago still are run by some nodes, storing 10 copies on these small altchains, checking regularly and look for a new coin if one gets really offline, should be several orders of magnitude cheaper than on BTC.

Data storage isn't really the problem. The problem are NFT waves, that's different from economics perspective.

ABCbits
Legendary
*
Offline Offline

Activity: 3458
Merit: 9509



View Profile
December 23, 2025, 07:48:06 AM
 #22

For other reader, such thing is already possible even before SegWit/Taproot exist and OP_RETURN limit raised.


That is false. File sharing was NEVER a supported use case of bitcoin, until core 30 anyways

We're talking about two different thing. I mentioned there are ways to add arbitrary data (even without SegWit, Taproot or OP_RETURN). But your respond is about whether Bitcoin support file sharing feature.

You could post a file on bitcoin only by obfuscating it to make it look like a genuine bitcoin transaction. Even OP admits thus much. Thought the rest of his childish and ridiculous monster analogy is pure bullshit.

About obfuscation, i already mentioned most wallet and average block explorer doesn't show/decode arbitary whether it use OP_RETURN or other approach. So to average people, all approach appear to be hidden/obfuscated. In addition, those approach considered as standard transaction, so they don't need to request miner to add their non-standard TX manually or semi manually.

IsraelK
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
December 23, 2025, 11:44:56 AM
 #23

Would be nice to store a PGP-encrypted message containing SEED phrase in OP_RETURN. With the current OP_RETURN size limit the encrypted message would require more than dozen transactions to accommodate it. First, this is costly. Second, it's inconvenient to reassemble the message for decryption. Lifting this limit would allow the relevant encrypted message to be stored on the blockchain in a single transaction. Real bargain.Smiley




It sounds convenient, but the OP_RETURN size limit is intentionally small to protect Bitcoin’s decentralization. Allowing large encrypted payloads would encourage blockchain bloat, increase long-term storage and bandwidth costs for all nodes, and turn Bitcoin into a general data-storage system. The cost and inconvenience you mention are deliberate disincentives. Also, storing a seed phrase on-chain—even PGP-encrypted—creates a permanent risk if the encryption is ever broken. Safer practice is to keep sensitive data off-chain and, at most, anchor a hash or reference on the blockchain rather than lifting the OP_RETURN limit
gmaxwell
Moderator
Legendary
*
expert
Offline Offline

Activity: 4620
Merit: 10258



View Profile WWW
December 23, 2025, 04:43:29 PM
Last edit: December 23, 2025, 04:54:22 PM by gmaxwell
 #24

I don't believe Bitcoin is particularly cheap as a data storage. Even if you add the "forever" word and limit yourself to blockchains which may be able to compete with paper for longevity. Solana, BSV, and other chains are much cheaper. And judging by the fact that even minuscule altcoins from 10 years ago still are run by some nodes, storing 10 copies on these small altchains, checking regularly and look for a new coin if one gets really offline, should be several orders of magnitude cheaper than on BTC.
As I pointed out in an earlier thread, if you create a model for 'forever' that involves paying into an investment account then using the dividends to pay for S3, -- it turns out that even Amazon S3 'forever' is orders of magnitude cheaper.  Between that and the other blockchains, as you note, it means anyone putting data in Bitcoin is almost certainly motivated by what they consider a compelling reason to do so.  Which is why speedbumps are not very effective, why they're willing and able to just directly pay miners and bypass any relay policy, etc.

This isn't to say that I agree with their motivations or like their motivations-- just that they exist, and their existence overcomes any amount of pepe's spam derangement syndrome.

The biggest of these motivations is that using Bitcoin limits the supply of tokens-- the other alternatives that are much cheaper do not.  Because of this limits in Bitcoin that inhibit NFTs have a real risk of making NFTs in Bitcoin *more* valuable or otherwise just canceling themselves out.

Certainly all the blather about it is an astonishing amount of free advertisement that they couldn't otherwise get at any price-- and that's worth pretty much any amount of transaction fees.  For the last year the biggest promoters of NFT crap have essentially been the ocean-affiliated pro-censorship crowd and their buddies.  This is another big advantage they get by using Bitcoin-- but unlike the limited supply it's one we don't have to give them.
PepeLapiu
Member
**
Offline Offline

Activity: 209
Merit: 72


View Profile
December 23, 2025, 04:54:12 PM
Last edit: December 24, 2025, 01:52:53 PM by mprep
 #25

It sounds convenient, but the OP_RETURN size limit is intentionally small to protect Bitcoin’s decentralization. Allowing large encrypted payloads would encourage blockchain bloat, increase long-term storage and bandwidth costs for all nodes, and turn Bitcoin into a general data-storage system. The cost and inconvenience you mention are deliberate disincentives. Also, storing a seed phrase on-chain—even PGP-encrypted—creates a permanent risk if the encryption is ever broken. Safer practice is to keep sensitive data off-chain and, at most, anchor a hash or reference on the blockchain rather than lifting the OP_RETURN limit

What you are talking about is simple logic. They won't understand what you are talking about.
In order for coretards to understand what you say, you have to think like them. You have to do absolutely nothing about the 4 year long current spam attack, and you have to talk about spam as if it were an unstoppable force of nature.

They think they can't stop spam, while they are actively rejecting new ordinal filters, and blowing up the op_return filter. And so they think the only way to deal with spam is to create more ways to spam.

And most importantly, you have to treat every anti-spam measure as it it were censorship. If anyone tries in any way to stop coretards from posting dickbutt jpegs, that's censorship akin to censoring all Iranian UTXO's or all non-OFAC compliant UTXOs. Because coretards think node runners don't know the difference between dickbutt jpegs and Iranian UTXO's.

Is that your alt account you're talking to, Pepe? Grin Thanks for bumping my thread anyway for free Smiley

If you care about people viewing your stupid monster analogy, you should move it to the General section where 5x more people will see it. Here in the Dev & Tech section a lot less people will see your thread, and they don't care as much about spam in this section.

But the spam promoting mods are likely to move it back to a lesser section again. However since you are promoting spam, your thread has a higher change of not getting moved around.

Quote
Seriously, do you think swearing will make your arguments look more intelligent?

So you want to promote spam AND you want respect? Sorry cupcake, that's not going to happen. You have to pick one or the other.


Quote
The trouble is actually caused to nodes who have too strict datacarriersize configurations, as these have to re-download the transactions they previously "filtered" and then rejected, causing them higher bandwidth costs. Miners?

The most important duty of the nodes is to regulate the miners. The nodes do that by verifying that the blocks are valid, and by filtering spam.

But you are claiming if the nodes just learn not to filter and to go along with whatever the miners want to mine, no matter how spammy, than the nodes will have an easier job.

This retarded idea that nodes have to go along with miners and bend the knee to spam, it's pure post modernist bullshit.


Quote
I don't believe Bitcoin is particularly cheap as a data storage. Even if you add the "forever" word and limit yourself to blockchains which may be able to compete with paper for longevity.

Call Google and ask them how much they charge to store whatever file you want, until the end of time, even after you die, on 90,000 separate Google servers for redundancy. And tell them that you reserve the right to submit whatever material you want, without them monitoring how illegal/gross/immoral your data is.

Quote
Solana, BSV, and other chains are much cheaper.

They are all scams. Everyone knows it. Spammers want to put their filth on the only legit and original real blockchain. And the coretards ate bent on making it easier for them to do so.

But your idea that spam is not a problem, that miners filling their blocks with spam, that's not a problem either. That the real problem is nodes filtering spam and not going along with what miners want, that falls in line with the core policy they impose on all their nodes.

As I pointed out in an earlier thread, if you create a model for 'forever' that involves paying into an investment account then using the dividends to pay for S3, -- it turns out that even Amazon S3 'forever' is orders of magnitude cheaper.

Wonderful! Now how about you call Amazon and ask them if they will allow you to upload any sort of illicit/immoral/illegal files on 90,000 servers, and keep it forever for you.

Ask them if they moderate child p**n, snuff, rape stuff, and other disgusting stuff.

Because since core 30, bitcoin will do that for you. Thank you, coretards!

Quote
This isn't to say that I agree with their motivations or like their motivations

You can claim all day that you disagree with spam. But your actions speak louder than your claim.

- You elude that filters are a form of cebsorship. When you, yourself, wrote in some of those filters.
- You shill for core removing a filter.
- You insult and resist every simple attempt at fighting spam

Your actions say it all, you are a spam shill.

Quote
Between that and the other blockchains, as you note, it means anyone putting data in Bitcoin is almost certainly motivated by what they consider a compelling reason to do so.  Which is why speedbumps are not very effective, why they're willing and able to just directly pay miners and bypass any relay policy, etc.

That is such bullshit. There are around a dozen filters already running on core since forever. Except the one core just neutered.

And if you look back, you will see that 99.99% of the transactions miners put in their blocks go along with the filters widely applied by nodes. Filters work. Stop repeating this bullshit that they don't work.

In fact the coretard logic is pretty transparent:

- "The filters don't work, but we have to turn off the filters because they prevent us from doing what they are filtering for."

So tell us cupcakes, if the filters don't work, why do we have to turn them off? If the filters don't work, why doesn't citrea just use the large op_return with the filters up?
- Because, obviously, filters work.

Quote
Certainly all the blather about it is an astonishing amount of free advertisement that they couldn't otherwise get at any price-- and that's worth pretty much any amount of transaction fees.  For the last year the biggest promoters of NFT crap have essentially been the ocean-affiliated pro-censorship crowd and their buddies.  This is another big advantage they get by using Bitcoin-- but unlike the limited supply it's one we don't have to give them.

Spammers stay on bitcoin because:
- They finance core
- Core did nothing about spam for the last 4 years since it started.
- Core lead dev doesn't even acknowledge there is such a thing as spam. She refers to it as "use cases we have today" and she claims that Satoshi failed to make room for it.
- Core sent as far as blowing up a spam filter.
- You coretards keep parroting that fighting spam is censorship.



Here is the reality. All the Amazon servers and Google drives of this world won't allow you to upload illicit, illegal, or sensitive material. They don't want to be held liable for that stuff. So they filter all the content that gets uploaded.

Go ahead, call Amazon and ask them to host child p**n forever on 90,000 Amazon servers. See how much they are willing to charge you for that service.

Because core 30 will do it for you. They'll force the 90,000 nodes to host your filth for free and for eternity. And for practically free too!

That's when the coretards come in and say "They could always do that all along"

Explain how, coretards. Give specific details. Will you break the file into 40 smaller pieces, and obfuscate the 40 pieces to make them look like a genuine transaction? Something that no antivirus and no drive scan will ever recognize as child p**n?

Will you go to a miner and offer him a fee to post your child p**n? Because they won't do that!

Will the file be contiguous, like in a blown up op_return?

I want details, exactly how "that was always possible"?


[moderator's note: consecutive posts merged]

Bitcoin is not a dickbutt jpeg repository.
Join the fight against turning bitcoin into spamware.
BitcoinKnotsForum.com
stwenhao
Hero Member
*****
Offline Offline

Activity: 574
Merit: 1357


View Profile
December 24, 2025, 07:10:23 AM
 #26

Quote
for free
Assuming 0.1 sat/vB, 1 BTC for 1 GB is not "for free".

Quote
for eternity
Not "for eternity", because a lot of nodes are pruned.

Quote
I want details, exactly how "that was always possible"?
Before transaction standardness was introduced, you could use just OP_PUSH, to upload anything in a single chunk. Also, your transaction could have zero fee in 2009, and it was possible to spend coins, which are unspendable today, by using "OP_TRUE OP_RETURN" in your input Script.

Quote
Will the file be contiguous, like in a blown up op_return?
Sure, in the old days, your scriptPubKey could contain any garbage, which today could be unspendable, but then, you could move it with "OP_TRUE OP_RETURN". As well as every other coin in the chain, without any signatures. Try 0.1.0 version from Satoshi, if you don't believe me. Of course, to test it, you would need Windows XP, or some virtual machine with it, and at least two connected nodes, even locally.

Also, in the old times, DER signatures could contain any data at the end. They were simply ignored, and accepted as valid.

Proof of Work puzzle in mainnet, testnet4 and signet.
PepeLapiu
Member
**
Offline Offline

Activity: 209
Merit: 72


View Profile
December 24, 2025, 07:41:35 AM
Merited by ertil (1)
 #27

Assuming 0.1 sat/vB, 1 BTC for 1 GB is not "for free".

I said THE NODES are forced to host that shit for free for the rest of time. The miners get paid to add it to their block. But the nodes, regardless of what filter they run, still have to host it.

Quote
Not "for eternity", because a lot of nodes are pruned.

You are being pedantic. If the chain is, say 5 TB because of the spam in 5 years, you will need a 5 TB drive to download the entire chain before you can prune it. And you still will have to download every single full block before you can prune them. And you are no longer a fully functional full node, which is a centralisation risk.

Quote
Before transaction standardness was introduced, you could use just OP_PUSH, to upload anything in a single chunk. Also, your transaction could have zero fee in 2009, and it was possible to spend coins, which are unspendable today, by using "OP_TRUE OP_RETURN" in your input Script.

Let me rephrase my question. The coretards always love to claim that uploading illicit data was always possible. So how would you do it the day before core 30 was released?

Specific step by step details, please. Explain it to me like I'm 8 years old.

Quote
Sure, in the old days, your scriptPubKey could contain any garbage, which today could be unspendable, but then, you could move it with "OP_TRUE OP_RETURN". As well as every other coin in the chain, without any signatures. Try 0.1.0 version from Satoshi, if you don't believe me. Of course, to test it, you would need Windows XP, or some virtual machine with it, and at least two connected nodes, even locally.

V0.1.0 on XP? Are you serious?
Explain in details how you would do it, the day before core 30 release.

Quote
Also, in the old times, DER signatures could contain any data at the end. They were simply ignored, and accepted as valid.

Would that be V0.1.0? Or V0.1.1?
Seriously man!

Give me specific details. What wallet would you use the day before core 30 release. Which miner would you call? How would you construct your transaction exactly?

Bitcoin is not a dickbutt jpeg repository.
Join the fight against turning bitcoin into spamware.
BitcoinKnotsForum.com
ertil
Member
**
Offline Offline

Activity: 118
Merit: 209


View Profile
December 24, 2025, 08:03:08 AM
Merited by vapourminer (1), ABCbits (1)
 #28

Quote
If the chain is, say 5 TB because of the spam in 5 years, you will need a 5 TB drive to download the entire chain before you can prune it.
No. Pruning is done continuously. If you set it to 2 GB, then only 2 GB of blocks will ever be saved. Then, old blocks will be removed, to make a room for new ones.

Quote
And you still will have to download every single full block before you can prune them.
Only in today's version. And even today, many people don't do that. Also, many users use utreexo, or other kinds of nodes, where it is not required.

Not to mention that you need to do it only once. Later, you can trust your own node, because if you cannot, then your whole setup is unsafe.

And even if you assume, that you have to download it, then still: it is not something, which is easily accessible by the outside world, because when your node is in Initial Blockchain Download mode, then it doesn't share blocks outside. It starts doing so, after downloading everything. And if pruning is enabled, then guess what: it will share only the last 288 blocks, or something like that, to the outside world.

Which means, that if some spam has for example 2000 confirmations, and was done two weeks ago, then it will never be shared by pruned node to the outside world. Because even if you set your pruning to 200 GB, then still, only 288 blocks will be shared to the outside world, for privacy reasons.
PepeLapiu
Member
**
Offline Offline

Activity: 209
Merit: 72


View Profile
December 24, 2025, 03:24:35 PM
Merited by stwenhao (1)
 #29

Stop making excuses. If you run a pruned node, you are running a crippled node that can't do it's full job like a full node does. The network needs more listening full nodes .Not half baked neutered pruned nodes.
 
No. Pruning is done continuously. If you set it to 2 GB, then only 2 GB of blocks will ever be saved. Then, old blocks will be removed, to make a room for new ones.

In don't believe that is correct.


Bitcoin is not a dickbutt jpeg repository.
Join the fight against turning bitcoin into spamware.
BitcoinKnotsForum.com
stwenhao
Hero Member
*****
Offline Offline

Activity: 574
Merit: 1357


View Profile
December 24, 2025, 06:31:44 PM
 #30

Quote
In don't believe that is correct.
Then, how my node with 40 GB hard disk could be synced? Do you think it magically stored 700 GB with 40 GB capacity somehow?

Also, what prevents a node from removing validated data? If the chain has 100k blocks, then it can be verified with the same algorithm, as if it has 200k blocks. Pruning can be set at any point in time: if there are too many blocks, then they will be removed. If there is not enough, then future blocks will fill that space.

Quote
The network needs more listening full nodes
Only because of Initial Blockchain Download. Otherwise, they wouldn't be needed, because each user could store its own transactions, and not care about the rest. Because nodes don't have to store transactions: they only need to know, that the chain is valid. If it wouldn't be the case, then altcoins like Monero wouldn't exist at all.

Quote
Not half baked neutered pruned nodes.
Still, pruned nodes, or even utreexo nodes, are better than SPV nodes. It is better to provide these half-baked nodes, because otherwise, many users would do, what they always do in such cases: if verification is too complicated, then they just skip it altogether.

Proof of Work puzzle in mainnet, testnet4 and signet.
gmaxwell
Moderator
Legendary
*
expert
Offline Offline

Activity: 4620
Merit: 10258



View Profile WWW
December 24, 2025, 06:50:35 PM
Merited by vapourminer (1)
 #31

No. Pruning is done continuously. If you set it to 2 GB, then only 2 GB of blocks will ever be saved. Then, old blocks will be removed, to make a room for new ones.
In don't believe that is correct.
It is correct, you can happily bring up and run a node on a system with a 20gb drive today with no issues and you've been able to do so since ~2013.

For all your crying about node resource use that really should be something you care about and know-- it makes me wonder if you've ever used bitcoin or if you really are just some paid disruption and not just the pervert obsessed with non-existing child abuse images that you appear to be on the surface.
d5000 (OP)
Legendary
*
Offline Offline

Activity: 4508
Merit: 10037


Decentralization Maximalist


View Profile
December 24, 2025, 07:23:15 PM
Merited by JayJuanGee (1)
 #32

So you want to promote spam AND you want respect? Sorry cupcake, that's not going to happen. You have to pick one or the other.
I think you're shooting yourself in the feet with that writing style, that's all. People will simply draw their own conclusions.

The most important duty of the nodes is to regulate the miners. The nodes do that by verifying that the blocks are valid, and by filtering spam.
True, but as long as consensus rules are not changed, nodes can't do anything about blocks which were already mined and are respecting the protocol.

Nodes (like Knots nodes with default configuration) that try to impose their own policy rules, will have to download blocks without the compact block benefit. That's simply how it works, not how I want it to work (or Core). These nodes simply have to accept to have higher bandwidth costs, according to the current protocol.

You would thus need to build a forking option into Knots (or whatever client). But that's not gonna happen. Nobody with a sane mind will run a node with crappy amateur code which only generates chaos confiscating all types of coins, like BIP-444 or "The Cat".

I repeat: Come up with a filtering mechanism based on consensus (not mempool policy) which doesn't confiscate existing coins and doesn't cripple features like Lightning, and we could be talking Smiley

This retarded idea that nodes have to go along with miners and bend the knee to spam, it's pure post modernist bullshit.
It's the Bitcoin protocol as Satoshi envisioned it (yeah, I know, shameless namedropping). Get over it Cheesy

Call Google and ask them how much they charge to store whatever file you want, until the end of time, even after you die, on 90,000 separate Google servers for redundancy. And tell them that you reserve the right to submit whatever material you want, without them monitoring how illegal/gross/immoral your data is.
I have purposefully not mentioned any cloud based solutions so this comment is pointless.

They are all scams. Everyone knows it. Spammers want to put their filth on the only legit and original real blockchain.
I even agree with this, but the incentive mechanisms are there for these chains to be up for decades or even centuries. And I would even say: if big altcoins die, then Bitcoin is also close to die.

But your idea that spam is not a problem,
No, that's not "my idea", and I have repeated that several times, including in the OP. My point was always: spam is a problem, but dealing with it without harming Bitcoin is a challenge.

Do your accept that challenge? Then work on a proposal like I wrote above: a proposal which makes spam more expensive but without confiscating coins/UTXOs. Or tools to delete meaningless spam UTXOs from nodes (note the difference to "The Cat"). I've already dropped some ideas, or ACK'd ideas from others, like @franky1's idea to enforce dust limits by consensus.

I think you're panicking because everything I wrote in the OP has become true until now, less the part where I expect a small spam wave. So the narrative of you folks is imploding.

That doesn't mean such a spam wave couldn't still happen. Some in that camp are perhaps really that angry that they will now coordinate a spam wave, perhaps when Core 30 share > Knots share (now Knots still has some percenage points more).

PepeLapiu
Member
**
Offline Offline

Activity: 209
Merit: 72


View Profile
Today at 04:31:21 AM
Last edit: Today at 09:54:21 AM by PepeLapiu
 #33

I think you're shooting yourself in the feet with that writing style, that's all. PIeople will simply draw their own conclusions.

Jesus Christ, man! Listen to yourself.

They are removing a spam filter.

THAT WILL RESULT IN MORE SPAM.

They rejected Luke's spam filter based on retarded made up excuses.

THAT WILL RESULT IN MORE SPAM.

They don't even acknowledge there is spam, the core head dev calls it "use cases we have today" that Satoshi failed to foresee.

THAT WILL RESULT IN MORE SPAM.

They removed the definition of bitcoin as money from their documentation and I can't find the word money or currency anywhere in their docs.

THAT WILL RESULT IN MORE SPAM.

The head core dev is giving bitcoin maximalists the thumbs down and giving NFTs the thumbs up.

THAT WILL RESULT IN MORE SPAM.

Every time we say the word spam, they move us to a section with fewer eyeballs.

THAT WILL RESULT IN MORE SPAM.

They called a spam filter that was running for 11 years censorship.

THAT WILL RESULT IN MORE SPAM

They equate Knots' spam filters to censorship.

THAT WILL RESULT IN MORE SPAM.

They are saying that nodes should align their mempool with what miners want to put in their blocks.

THAT WILL RESULT IN MORE SPAM.

Quote
This retarded idea that nodes have to go along with miners and bend the knee to spam, it's pure post modernist bullshit.
It's the Bitcoin protocol as Satoshi envisioned it (yeah, I know, shameless namedropping). Get over it Cheesy

Citation needed.

Quote
No, that's not "my idea", and I have repeated that several times, including in the OP. My point was always: spam is a problem, but dealing with it without harming Bitcoin is a challenge.

Do your accept that challenge? Then work on a proposal like I wrote above: a proposal which makes spam more expensive but without confiscating coins/UTXOs. Or tools to delete meaningless spam UTXOs from nodes (note the difference to "The Cat"). I've already dropped some ideas, or ACK'd ideas from others, like @franky1's idea to enforce dust limits by consensus.

Here's what on my to-do list:
- Mark core as deprecated, they pretty much did it to themselves already.
- Fight spam at all levels, including at the policy level with Knots filters.
- Fight spam at the consensus level, including with BIP 110
- Fight spam at the UTXO set level with The Cat. And go to hell for even suggesting we should play by the rules and be nice to spammers who use fake pubkeys, fake scripthash, and always just above the dust limit to fool the system into thinking they are monetary transactions.

But since you want to fight it strictly at the consensus level, look into BIP 110, and support the raising of the dust limit at consensus level. I personally would prefer to go with 50,000 sats, and to expire in 5 years. But 5,000 sats dust limit would be an easier sell. Still, I guaranty you, coretards and Maxwell will find a way to resist that one too at all levels, like they have for every other attempt to fight spam.


Bitcoin is not a dickbutt jpeg repository.
Join the fight against turning bitcoin into spamware.
BitcoinKnotsForum.com
PepeLapiu
Member
**
Offline Offline

Activity: 209
Merit: 72


View Profile
Today at 09:00:04 AM
 #34

No. Pruning is done continuously. If you set it to 2 GB, then only 2 GB of blocks will ever be saved. Then, old blocks will be removed, to make a room for new ones.
In don't believe that is correct.
It is correct, you can happily bring up and run a node on a system with a 20gb drive today with no issues and you've been able to do so since ~2013.

For all your crying about node resource use that really should be something you care about and know

Gosh! Thank you for that info. Now since having the full chain is not important at all, I's going to go chop off most of it on my node and only carry the last 2000 blocks, okay!

And since I also learned from you and the rest of the coretards that filters don't work if there is an economic incentive to go around them, I'm going to turn off all my filters now. Even the ones working for the last 15 years or so. Because, you know, censorship!

And well, without filters, what's the point of even running a mempool? So I'm going to yank that out of my node too!

And as you already pointed out, spammers can get around the consensus rules proposed by BIP 444/110. So, I'm going to yank those too out of my node!

[/sarcasm]

It's a real shame that you and I won the block war over the idea that fully operating nodes are vital to the survival of bitcoin. And now you are going around diminishing every aspect of running a node.

Quote
it makes me wonder if you've ever used bitcoin or if you really are just some paid disruption and not just the pervert obsessed with non-existing child abuse images that you appear to be on the surface.

I'm not very smart or knowledgeable, I get by on my looks alone. From your looks, I gather you are a freaking genius.

Bitcoin is not a dickbutt jpeg repository.
Join the fight against turning bitcoin into spamware.
BitcoinKnotsForum.com
DaveF
Legendary
*
Offline Offline

Activity: 4074
Merit: 7025



View Profile WWW
Today at 02:40:53 PM
 #35

....I'm not very smart or knowledgeable, I get by on my looks alone. From your looks, I gather you are a freaking genius.

Well he is a well known programmer, published author, has several patents, amongst other things.
And uses his own name.

You on the other hand claim to be a talking skunk.


-Dave


This space for rent.
PepeLapiu
Member
**
Offline Offline

Activity: 209
Merit: 72


View Profile
Today at 05:04:19 PM
Last edit: Today at 05:42:11 PM by PepeLapiu
 #36

....I'm not very smart or knowledgeable, I get by on my looks alone. From your looks, I gather you are a freaking genius.

Well he is a well known programmer, published author, has several patents, amongst other things.
And uses his own name.

You on the other hand claim to be a talking skunk.
When you say amongst other things, do you mean shilling for spam, rejecting every attempt at cutting spam, and trying to portrait nodes as basically useless?

Sorry to break this to you - talking skunks don't exist.
I know it sucks that you can't attack my person, right?

Greg Maxwell is doing a 180 from the block war small block argument - he is trying to minimize the role of nodes, like the rest of the coretards.

You are all shilling for pruned nodes, because the full blockchain is not important. You are all shilling for the removal of spam filters because 99.9% effectiveness is not good enough. And you are all cheering core in their statement that nodes should align their mempool with what miners want to put in their blocks.

Fight spam at the mempool level? - "NOOO, cant's do that, that's Knotzism!" says the coretard.
Fight spam at the consensus level with BIP 110? - "NOOO, can't do that, that's useless!" says the coretard.
Fight spam at the UTXO set level with The Cat or The Lynx? - "NOOO, can't do that, it's the same as banning Iranian UTXOs!" says the coretard.
"But what is spam, anyways?" says the coretard.

You coretards are so obvious.

Piling every proof-of-work quorum system in the world into one dataset doesn't scale.

Bitcoin and BitDNS can be used separately.  Users shouldn't have to download all of both to use one or the other.  BitDNS users may not want to download everything the next several unrelated networks decide to pile in either.

The networks need to have separate fates.  BitDNS users might be completely liberal about adding any large data features since relatively few domain registrars are needed, while Bitcoin users might get increasingly tyrannical about limiting the size of the chain so it's easy for lots of users and small devices.
 
Now, re-read the quote above and replace all instances of BitDSN with the word spam.

Bitcoin is not a dickbutt jpeg repository.
Join the fight against turning bitcoin into spamware.
BitcoinKnotsForum.com
DaveF
Legendary
*
Offline Offline

Activity: 4074
Merit: 7025



View Profile WWW
Today at 06:43:12 PM
 #37

....
I know it sucks that you can't attack my person, right?
......

No, I can't attack you as a person. But, then again I don't want to. Personally you don't matter to me one way or the other.
You seem to be happy being an anonymous troll so that is more or less what you are in my mind.

Your ideas of what you want to do, those I can attack.
You have shown that you want to block some transactions that you do not like.
And that is easy to attack.

You don't like some transactions since they are pictures or whatever and you don't think they should be in the blockchain.
I don't think any transactions going to PepeLapiu should be in the blockchain.
There is zero difference between those 2 things. Someone is paying a miner to put data they want into the blockchain.
Miners, are doing their job and putting in what people pay to put in so long as they are valid TX.

That's it, plain and simple. Pure capitalist economics at it best.

You want some kind of regulated by 'people who know better' socialism where everyone gets space in the chain. Even if they can't pay or don't want to pay more to get in because the current blocks are filled with what you consider spam. I just like the pictures.

-Dave



....Sorry to break this to you - talking skunks don't exist......


With the amount of post surgical pain killers I'm on, I disagree. They most definitely exist. Heck I just saw some weird alien looking guy muttering something about
"Where's the kaboom? There was supposed to be an Earth-shattering kaboom!"



This space for rent.
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!