As far as network integrity goes, Is there anything wrong with accepting low tx

[Xenland]

As far as network integrity goes, Is there anything wrong with accepting low to none tx fee transactions only? (Low being 0.00005)

[1714916445]

1714916445

[1714916445]

1714916445

[Xenland]

I mean /verifying/mining.... etc you know

[Revalin]

Should be fine but you shouldn't expect a lot in fees.

[deepceleron]

You also shouldn't expect too many fee-requiring transactions to get to your miner if they are paying less than .0001 BTC/KB, as that is the relay threshold, unless you publish your node IP so freeloaders can directly connect to you.

If transactions can be free, it makes spamming a million transactions almost free, which is why the minimum fee is mandatory for transactions under .01 BTC. Miners have an ethical responsibility to include transactions in a timely manner if they comply with network rules, and promote fee rewards with quick inclusion for extra fees paid, while keeping cheap junk out of the now-5GB of blockchain p2p downloading that burdens client installation.

If your client accepts any amounts of free transactions relayed to it, it also must keep all transactions in the memory pool until included in a block, which exposes Bitcoin to another DDOS vector - by sending you gigs of spam transactions directly, your memory can be used up.

[Xenland]

You also shouldn't expect too many fee-requiring transactions to get to your miner if they are paying less than .0001 BTC/KB, as that is the relay threshold, unless you publish your node IP so freeloaders can directly connect to you.

If transactions can be free, it makes spamming a million transactions almost free, which is why the minimum fee is mandatory for transactions under .01 BTC. Miners have an ethical responsibility to include transactions in a timely manner if they comply with network rules, and promote fee rewards with quick inclusion for extra fees paid, while keeping cheap junk out of the now-5GB of blockchain p2p downloading that burdens client installation.

If your client accepts any amounts of free transactions relayed to it, it also must keep all transactions in the memory pool until included in a block, which exposes Bitcoin to another DDOS vector - by sending you gigs of spam transactions directly, your memory can be used up.

Thanks for that informative answer