Marker denom restrictions

[iramiller]

Summary

In order to prevent spamming the network with denoms of coin that overlap with other well known values [BTC, ETH, etc] the marker module should enforce additional restrictions on coins created directly while keeping the constraints relaxed for governance proposal based coins.

Problem Definition

With any user being able to cheaply and quickly create new coins on the provenance blockchain there is a concern that there maybe confusion from coins being created that trivially match existing currencies on other networks. Despite this concern the flexibility to create coins with short or well known names should be maintained. Using a whitelist or other similar heuristic would also prevent difficulties in maintenance, complexity, and completeness.

Proposal

The simplest solution to the problem appears to be to create a couple new validation parameters for denom names

• General Validation Expression (set to[a-f].[0-9a-f]{9,39} or similar to allow a hexidecimal denom that does not start with a number and is 10 to 40 in length)
• Ensure a governance proposal to create a marker is not subject to the above restriction
• Put the restrictions into parameters that can be configured in genesis or through parameter change proposals

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[iramiller]

It is probably useful to categorize short denoms as "symbols" in user interfaces and related nomenclature. Examples of these would be typical coins and investment fund names. The longer, less restricted names would remain referred to as generic "denoms".