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

Dust limit set up when filling Genesis metadata #36

Closed
UkolovaOlga opened this issue Jun 24, 2020 · 2 comments
Closed

Dust limit set up when filling Genesis metadata #36

UkolovaOlga opened this issue Jun 24, 2020 · 2 comments
Labels
enhancement New feature or request [RGB] Specs related to client-validated state management system

Comments

@UkolovaOlga
Copy link
Member

Designing RGB smart contracts table

Questions:

  1. Do we need to set it at all?
  2. Is it present in Confidential Assets?
  3. What is the reasonable upper bound for “Dust limit” value?
@UkolovaOlga
Copy link
Member Author

Is dust limit present in CA?

The minimum amount of an asset you can issue is 0.00000001. This is also the smallest amount of any issued asset that you can send. The minimum amount of the default asset that you can send (L-BTC) is higher, at 0.00001. These differ as the default asset considers the minimum send amount of the Bitcoin network’s dust limit. The maximum amount of an asset you can issue is 21,000,000 although more can be created by reissuing. When you create the reissuance token as above, where the amount was 1, you are actually creating 100,000,000 of them when measured in their smallest denomination. This is because they are divisible like every other asset on Liquid. The 1 is little more than a user interface concession. For ease of readability we will refer to this issuance as “one token”.

https://docs.blockstream.com/liquid/developer-guide/issued-assets.html?highlight=dust

@dr-orlovsky dr-orlovsky transferred this issue from LNP-BP/devcalls Jul 12, 2020
@dr-orlovsky
Copy link
Member

Decision from the last call: remove dust limit

@dr-orlovsky dr-orlovsky added this to the RGB schemata milestone Sep 15, 2020
@dr-orlovsky dr-orlovsky added enhancement New feature or request [RGB] Specs related to client-validated state management system labels Sep 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request [RGB] Specs related to client-validated state management system
Projects
None yet
Development

No branches or pull requests

2 participants