Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Can a declined transaction cost multiple fees due to seqno not incrementing?

I have a question that might be silly. If I get it right, declined transactions do not increment the seqno of the sender wallet. Can it lead to a situation when I try to programmatically send more value than I own, and since the seqno does not get incremented and the task seems to be unfinished, the network keeps on trying to process it and I pay fees again and again? How many times may a user pay a fee in that scenario? What can be done to stop the network from processing the transaction?

This question was imported from Telegram Chat: https://t.me/tondev/125966

Votes Newest