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

RGB asset schemata: introduce minimum division for LN channels/micropayments #51

Closed
dr-orlovsky opened this issue Sep 15, 2020 · 5 comments
Assignees
Labels
enhancement New feature or request [RGB] Specs related to client-validated state management system

Comments

@dr-orlovsky
Copy link
Member

dr-orlovsky commented Sep 15, 2020

Use a metadata field to define a minimum division for asset payments inside LN channels (equivalent to msat)

@dr-orlovsky dr-orlovsky added enhancement New feature or request [RGB] Specs related to client-validated state management system labels Sep 15, 2020
@dr-orlovsky dr-orlovsky added this to the RGB schemata milestone Sep 15, 2020
@dr-orlovsky dr-orlovsky self-assigned this Sep 15, 2020
@BitcoinErrorLog
Copy link

Misc question, is there an actual need or notable utility to allowing special LN-only divisions?

I personally think people underestimate how divisibility affects economics and inflation...

I'm not saying that it is OUR problem what an issuer chooses to support, but I've always been negative towards adding units, even as decimal places.

@dr-orlovsky
Copy link
Member Author

One of use cases for LN are micropayments. For instance, with USDT, we certainly would have payments <$1; especially with IoT becoming more common (like paying per second of video clip). This will be impossible if we would not support LN-style divisibility unit which must be different from mainnet unit in this case.

@BitcoinErrorLog
Copy link

Is that to say that RGB doesn't already support decimal places in the genesis on chain? If so, sure, we need some decimal places, but I thought this is about having even more places on LN than on onchain, as your (msat) example.

For example, I do not think people will need $0.000 000 001 transactions ever, if they already have $0.000 000 01 as an option. At some point the cost of processing the amount in a verifiable cycle vastly exceeds the value of the txn.

@dr-orlovsky
Copy link
Member Author

No, this is not anyhow related to decimal places. Decimals are pure UI thing; internally all amounts are in smallest indivisible unit for a mainnet (like Satoshis in Bitcoin: you would not find bitcoins in bitcoin transactions). But yes; genesis defines how a large-scale unit can be composed from minimal unit with a special decimal parameter - exactly like it is done in Confidential Assets.

^^^
And this have nothing to do with the topic here, which is about micropayments in LN (equivalend of msats).

@dr-orlovsky
Copy link
Member Author

Follow-up from the dev call on the 7th of Oct 2020: we do not need a separate subdivision for this case: an issuer must carry about chosing the atomic unit (i.e. already existed divisibility of the main named unit of accounting)to be sufficient for micropayments (so in case of USDT it must be not a "cent", but "millicent" or something like that).

Related discussion: #60

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