ord icon indicating copy to clipboard operation
ord copied to clipboard

Published 20 hours ago • verified publisher icon ordinals

Don't allow a user to etch a rune if a valid reveal is in the mempool

Open casey opened this issue 4 months ago • 6 comments

casey avatar Mar 19 '24 00:03 casey

How do we handle low fees transactions that can be excluded from mempool or get stuck?

markovichecha avatar Mar 23 '24 12:03 markovichecha

I think this is probably relatively low priority, so not necessarily worth doing right away if it's too hard. The best option would probably be to only warn the user if a valid reveal is in the mempool with a higher feerate than the one the user selected, so they can out-bid it.

casey avatar Mar 23 '24 17:03 casey

Hello,

Did you removed wallet etch command? It can find it anymore and there are only 3 runes deployed. I need to make some deployment tests. Should I rewrite all the tx worklflow?

GaloisField2718 avatar Mar 27 '24 02:03 GaloisField2718

Runes are now etched with ord wallet inscribe --batch <BATCHFILE>. There are a bunch of parameters, so it isn't practical to specify them in command line arguments.

casey avatar Mar 27 '24 04:03 casey

Any requirements for batchfile? Also it will increase the confusion between Runes protocol and ordinal protocol no?

GaloisField2718 avatar Mar 27 '24 09:03 GaloisField2718

Should we maintain a separate index with mempool transactions? I guess it'll take too long if we'll do it on demand. If we are building an index we should enable ZeroMQ to subscribe on new transactions.

markovichecha avatar Mar 27 '24 22:03 markovichecha