Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Defining / closing seals on dust UTXO #31

Open
MaxHillebrand opened this issue Jul 11, 2020 · 0 comments
Open

Defining / closing seals on dust UTXO #31

MaxHillebrand opened this issue Jul 11, 2020 · 0 comments
Labels
[CSV] Client-side validation-related specs [RGB] Specs related to client-validated state management system
Milestone

Comments

@MaxHillebrand
Copy link
Member

A dust UTXO is uneconomical to spend, meaning that the value of sats it contains is below the mining fee in sat/vbyte that is required to spend it again. In order to spend the coin, it has to be consolidated with at least one other coin, that pays for the left-over transaction fee deficit.

IIRC, Bitcoin Core / Knots nodes remove such a coin from their UTXO set in memory, as it is not expected [but still possible] that it will be spent.

However, RGB changes this dynamic.

A seal can be defined on ANY UTXO [even a non-existing / LN output]. Thus, a seal can potentially be defined on a dust UTXO too. This means, that the "real" economical value of spending this coin is in fact higher than only the transfer of the sats, as it also closes the seal and thus transfers ownership of the RGB asset.

Questions

  • Should dust coins be prohibited from defining a seal upon?
  • Are there any nuances to consider when closing a seal over a dust coin?
  • Are there any issues with full nodes who don't have that dust coin in memory?
@dr-orlovsky dr-orlovsky added this to the CSV: drafts milestone Sep 15, 2020
@dr-orlovsky dr-orlovsky added [RGB] Specs related to client-validated state management system [CSV] Client-side validation-related specs labels Sep 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[CSV] Client-side validation-related specs [RGB] Specs related to client-validated state management system
Projects
None yet
Development

No branches or pull requests

2 participants