Create account

replied 1728d
The site tries to use all your UTXOs to get around the issue. Even with mitigations in place, users only have so many UTXOs and this limit still gets hit.
replied 1728d
Could you just automatically make more utxos? Auto-split balance into a bunch of .00001 utxos or something so that it’s way less likely you’ll run out of them.
replied 1728d
Additional mitigations can be put in place, but they require significant dev time and don't fix the root issue.
replied 1728d
Use your influence to get this on the next fork. But I wonder what implications it will have with mempool management and block verification time?
replied 1728d
I've been brining this up for almost a year. It's a miner setting, doesn't need a fork. https://jasonc.me/blog/chained-0-conf-transactions-memo
BCH
replied 1728d
All miners need to have the same setting in order to not get their blocks orphaned. FYI Bitcoin.com is working on a spec for this. I think during Nov upgrade this should be fixed.
replied 1728d
Is the plan to just roll back Core’s limit at the next upgrade like it never existed, or is there more to reverting the limit?
BCH
replied 1728d
The BCH Devs talk about this limit here:

Or maybe in the one before or after this one. Not sure which one and I won;t listen to them again now.
BCH
replied 1728d
And to answer your question, yes, it's not as easy as we like to think! There;s more to this than just turning a 25 to 100.
replied 1728d