Skip to main content
deleted 2 characters in body
Source Link
Raghav Sood
  • 17.3k
  • 3
  • 23
  • 43

In addition to Chytrik's mentionedmention of a dust attack, dust limit transactions are also used heavily by the Omni Layer to identify the recipient of an omni asset. Transactions such as those will follow pattern of one dust (or near dust) output, an OP_RETURN output, and a change output.

While dust attacks tend to create thousands of dust outputs in a handful of transactions, omni layer transactions will only create a single dust output per transaction.

In addition to Chytrik's mentioned of a dust attack, dust limit transactions are also used heavily by the Omni Layer to identify the recipient of an omni asset. Transactions such as those will follow pattern of one dust (or near dust) output, an OP_RETURN output, and a change output.

While dust attacks tend to create thousands of dust outputs in a handful of transactions, omni layer transactions will only create a single dust output per transaction.

In addition to Chytrik's mention of a dust attack, dust limit transactions are also used heavily by the Omni Layer to identify the recipient of an omni asset. Transactions such as those will follow pattern of one dust (or near dust) output, an OP_RETURN output, and a change output.

While dust attacks tend to create thousands of dust outputs in a handful of transactions, omni layer transactions will only create a single dust output per transaction.

Source Link
Raghav Sood
  • 17.3k
  • 3
  • 23
  • 43

In addition to Chytrik's mentioned of a dust attack, dust limit transactions are also used heavily by the Omni Layer to identify the recipient of an omni asset. Transactions such as those will follow pattern of one dust (or near dust) output, an OP_RETURN output, and a change output.

While dust attacks tend to create thousands of dust outputs in a handful of transactions, omni layer transactions will only create a single dust output per transaction.