Closed gmart7t2 closed 7 months ago
I think we fixed this in 0.18.0, but double check and make sure we didn't fuck it up 😅
Whoops, we definitely didn't fix this!
What about pub const COMMIT_CONFIRMATIONS: u16 = 6;
There are not found in any document or proposal, if the commit transaction and the reveal transaction in the same blockchain, how about it is?
https://docs.ordinals.com/runes/specification.html#etchings
To prevent front running an etching that has been broadcast but not mined, if a non-reserved rune name is being etched, the etching transaction must contain a valid commitment to the name being etched.
A commitment consists of a data push of the rune name, encoded as a little-endian integer with trailing zero bytes elided, present in an input witness tapscript where the output being spent has at least six confirmations.
If we wait for the commit to have 6 confirmations before sending the reveal, the reveal will have at least 7 confirmations when it confirms.