Reveal transaction error

[ordinalsbot]

Hi, We are having this error multiple times for a tx that actually went through and broadcasted but ord returned an error.

How can we track and fix these false negatives?

inscribing xxx/xxx_182.png fee 17 error: Failed to send reveal transaction because: JSON-RPC error: transport error: Couldn't connect to host: Resource temporarily unavailable (os erro r 11)

resulting duplicate inscriptions: https://ordinals.com/inscription/fc1adbf3c736a188552b6c787cb57533d3ad33d886a470a67254fd9a04bdb500i0 https://ordinals.com/inscription/b386154198ce5e817abf9c1ef7027e8d5209ef62a61dee21cc951a32083d4679i0

[soenkehahn]

Could you describe what exactly you did that resulted in this error, i.e. what command you ran, please? Especially I'm not sure whether you tried to inscribe this file twice or not. Did you try to inscribe the file once and ord inscribed the file twice?

[gmart7t2]

The txs were broadcast but ord reported that they weren't so he tried again, ending up with 2 copies.

[casey]

This issue is not actionable as is. In order to understand and fix this issue, the following questions need to be answered:

• What were you trying to do? Were you trying to inscribe?
• What commands did you run exactly and in what order?
• Why do you think there was a bug?
• Can this issue be reproduced?

I think I have an idea what you were trying to do and what the problem is, but I don't want to guess, and need a clear description of the issue in order to be able to solve it.

[ordinalsbot]

sure, I'll try to provide more information but not sure if it's something that can easily be reproduced:

• inscribe a file with fee and destination address: ord wallet inscribe someimagefile.png --destination bc1psometaprootaddress --fee-rate 17

we have done over 50k+ inscriptions and in our logs we see 26 occurances of this issue with below breakdown:

• Failed to send commit transaction -> 15 times:

  error: Failed to send commit transaction JSON-RPC error: RPC error response: RpcError { code: -26, message: "insufficient fee, rejecting replacement 8de xxx; new feerate 0.00005000 BTC/kvB <= old feerate 0.00006000 BTC/kvB", data: None }

• Failed to send reveal transaction: -> 11 times

  error: Failed to send reveal transaction JSON-RPC error: transport error: Couldn't connect to host: Resource temporarily unavailable (os error 11)

It could be that maybe a block is found during this time but it's difficult to say. when I compare our logging time with block times I think they are overlapping 2023-02-28T19:34:44.155Z (issue time) -> 2023-02-28 19:34 (block #778700 timestamp)

Note that we don't do anything on the DB in parallel so only 1 ord client has access to this machine

it can be possible to discover the issue on regtest by aggressively inscribing and mining blocks in parallel...

[casey]

I'm not sure we can debug this as is, if it occurs 26 times in 50k inscriptions.