Why not just raise the transaction fee to .0005 per transaction?? That will make the attack way more costly and the cost is still negligible to typical bitcoiners.
fuck it. have confirmation times 1 minute, and decrease block reward by the proportional amount. you dumb fucks sometimes you wait around 45 minutes for confirmations. how the fuck is that okay? Unless you don't want bitcoin to be used day to day for a coffee, sandwich, parking fees, beer, etc, etc, etc, etc,
That's the biggest minus of Bitcoin. Fucking long confirmation time.
This is not a bitcoin problem it is a math problem. Bitcoin (for good or bad) relies on math. The hope was that wallets would use math to calculate TX fees. Many do... apparently... yours does not. You might want to reconsider your choice of wallet programs, or do the math yourself. If you don't want to do the math, I would set your TX fee commiserate to your disdain for the math required. Again... switching wallets, or complaining to the wallet maker may be the easiest answer.
The transaction fee is a statistical question... As long as the entire mempool can fit in one block (which it can as of right now), you can go all the way down to 1 sat/byte.
The minimum TX fee to stay on the network (as of today) is 1000 sat / 1000 bytes (or 1 sat/byte).
If your TX has old coins, it is possible that the priority is high enough (as of today 57,600,000) to stay on the network with no TX fee
If the mempool is larger than one block (1,000,000 bytes) then your TX will need to compete with other TX to get in a block.
When transactions have to compete for blockspace the following sorting is used.
- The transactions are sorted by priority
- The highest priority (coin age) TX are selected until the block is 5% filled
- The remaining transactions are sorted by satoshi/byte
- Those payint the highest satoshi/byte are selected for the remaining 95% of the block space
- The rest of the TX are left into pool for the next sorting
If you studied statistics, this is straight forward problem to solve, but as others have stated about 76 times already... hard coding a fee value will not solve a statistical equation. Best to get a wallet app that is mempool aware with sliding fees, or do the stats yourself if the mempool ever fills up again.
The sample data to solve this simple statistical problem by hand is conveniently provided
here if you scroll down and select "
Raw Data"
PS: Admins... forgive my double post... just get weary of explaining it.