Over 100 Memo transactions rejected in the last 24 hours due to mempool limits. People run into this daily. When will they be raised?
Could you explain what the mempool limit is, and why it was created in the first place?
Also, the failures are @memo's fault if @memo does not provide a warning to the user.
Improving error messaging for these is planned. It's not as straight forward as you'd think though.
Bitchcoin trash engineers working hard on it.
Aumary deployed 4 monkeys.
Is there a reason why you have to chain the txs for regular use? Couldn’t you use any utxo? But I agree, the child limit is hurting dApps.
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.
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.
Additional mitigations can be put in place, but they require significant dev time and don't fix the root issue.
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?
Just raise the cost of memo post, as a temporary workaround. You may like it long term.
