✨ Accept only CT decimals from 4 to 20

[JuaniRios]

What?

• The decimals in the token information can now only be a number from 4 to 20 inclusive.

Why?

• Too low numbers means a very big whole part in the Fixedu128, too high means a very big decimal part in the same type.
• We want to make sure the price is representable

How?

• add a new check on the metadata validation function

Testing?

unaccepted_ct_decimals on the application test file

Anything Else?

• We need to also check that the allocation size is big enough to represent the decimals specified by the user. In another PR though

[JuaniRios]

• ⚡️ Add check for allocation smaller than decimals #280
• ✨ Accept only CT decimals from 4 to 20 #279 👈
• ✅ New decimals remainder test #278
• ✅ New decimals community test #277
• ✅ New decimals auction test #275
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @JuaniRios and the rest of your teammates on Graphite

[graphite-app]

Graphite Automations

"Auto-assign PRs to author" took an action on this PR • (05/01/24)

1 assignee was added to this PR based on Juan Ignacio Rios's automation.

[JuaniRios]

Merge activity

• May 2, 5:12 AM EDT: @JuaniRios started a stack merge that includes this pull request via Graphite.
• May 2, 5:19 AM EDT: Graphite rebased this pull request as part of a merge.
• May 2, 5:20 AM EDT: @JuaniRios merged this pull request with Graphite.