Skip to content

Explain the rationale behind 18 decimals format for RPS and snapshot amount #297

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.

Sign up for GitHub

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

Jump to bottom
Open
smol-ninja opened this issue Apr 8, 2025 · 0 comments
Open

Explain the rationale behind 18 decimals format for RPS and snapshot amount #297

smol-ninja opened this issue Apr 8, 2025 · 0 comments
Labels
effort: medium Default level of effort. priority: 3 Nice-to-have. Willing to ship without this. type: docs Changes to documentation. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise.

Comments

@smol-ninja
Copy link
Member

The "About Precision" section has been removed from the Flow repo in sablier-labs/flow#431. However, some of its content can be useful for developers into understanding why we use 18 decimals format for RPS and snapshot amount.

Therefore, we should document it somewhere in the Sablier docs (TBD), answering the following questions:

  1. Why does RPS use 18 decimals format instead of token's decimals?
  2. Why is scaling and descaling of amounts necessary in deposit and withdraw?

References

  1. About Precision section
  2. Why are we still keeping diagrams in this repository? flow#412
@smol-ninja smol-ninja added effort: medium Default level of effort. priority: 3 Nice-to-have. Willing to ship without this. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise. type: docs Changes to documentation. labels Apr 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort: medium Default level of effort. priority: 3 Nice-to-have. Willing to ship without this. type: docs Changes to documentation. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@smol-ninja