Error leaks to client: replacement transaction underpriced
When creating many MLS commits using XDBG such as cargo xdbg -b local -d generate --entity identity --amount 5, some of these might fail because of wrong pricing.
Some of these errors should not flow back to the client and should be retried by the payer.
Error:
0: API error: API client error: mls error: status: Internal, message: "error publishing group message: rpc error: code = Internal desc = error publishing identity update: replacement transaction underpriced", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc"} }
1: API client error: mls error: status: Internal, message: "error publishing group message: rpc error: code = Internal desc = error publishing identity update: replacement transaction underpriced", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc"} }
2: mls error: status: Internal, message: "error publishing group message: rpc error: code = Internal desc = error publishing identity update: replacement transaction underpriced", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc"} }
3: status: Internal, message: "error publishing group message: rpc error: code = Internal desc = error publishing identity update: replacement transaction underpriced", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc"} }
@fbac could I get a technical explanation of this one?
Is the fix as simple as retrying the transaction?
@fbac could I get a technical explanation of this one?
Is the fix as simple as retrying the transaction?
@mkysel a transaction in the mempool (not executed) can be replaced with other with the same nonce, but has to have a higher fee, so the miner takes it over the preceding one.
Without any context, I believe what happened here is that some transaction was posted to the blockchain. Before it was executed a new one was posted, with same nonce, same gas fees, and same private key originating it.
Closing this as complete as it's fixed now. The fix is a combination of factors such as enhancing the nonce manager, fixing the blockchain path, better blockchain methods, etc