RGB20: reduce asset name length limit

[zoedberg]

Currently there's an enforcement at schema level of 256 chars on the asset name.

This limit may be too high, so let's consider lowering it a bit.

[fedsten]

Which potential issues do you see by keeping the limit at the current level?

[zoedberg]

Which potential issues do you see by keeping the limit at the current level?

I think that usually asset names will be short (e.g. ticker: "USDT" -> name: "USD Tether").

IMO allowing 256 chars can't cause dangerous issues, but from an interface perspective, every developer in every software that wants to show that info, will have to consider that potentially someone created an asset with a very long name. That's not a funny thing to deal with, especially if most of asset names are short and just one isn't.

So I think we need a reason to keep it so long, not the opposite.

My suggestion is to use 32 chars, it should be enough.

[fedsten]

Fair point, I agree with the proposal of reducing the chars limit to 32

[St333p]

I agree, a 32 chars limit helps to clarify the intended purpose of the "name" field.

[weedcoder]

in liquid, there is no asset name. if you want to have a name, you have to register against blockstream registry and have some cryptographic proofs in a https served .well-know files. you can assign asset name manually in the client configuration file, not really practical. here is the documentation : https://docs.blockstream.com/liquid/developer-guide/proof-of-issuance.html

[nicbus]

• the longest currency name in wikipedia's List of circulating currencies is Bosnia and Herzegovina convertible mark with 39 characters
• the longest ERC20 token name (according to etherscan.io is Yee with 46 characters (Yee - A Blockchain-powered & Cloud-based Socia) or 40 when ignoring the leading Yee - (also, looks like it's been truncated)

the answer might be 42 :smirk:

[dr-orlovsky]

I think we need 37