Registered Assets list akin to tx list for Liquid

[alessandro-saglimbeni]

we are being asked for a section for Registered Assets on the explorer under Liquid.

It should be a list list (like the one for transactions https://blockstream.info/liquid/tx/recent) but for registered assets,

• Columns should be:

• "Name" (the name registered on asset registry)

• "Asset ID" (the full asset HEX 64 char)

• ordering should be alphabetical on "Name"

• paging should be the same as for the blocks section

• link to new page from somewhere

[shesek]

Columns should be:

How about the domain and ticker?

[shesek]

An initial page assets list page was implemented in eb4b019.

[alessandro-saglimbeni]

How about the domain and ticker?

They make sense yes, I wonder if all of these columns fit in the page? If they wouldn't the Ticker could be left behind.

The ideal order of the columns would be:
"Name" | "Ticker" | "Issuer" | "Asset ID"

[shesek]

For assets that don't have a name/ticker, should the column be left blank or filled with something like "None"?

[shesek]

They don't all fit in, but it can be made to work by truncating the asset id:

This is without the ticker (still doesn't fit in):

And the mobile view:

[alessandro-saglimbeni]

For assets that don't have a name/ticker, should the column be left blank or filled with something like "None"?

Yes "None" is fine

They don't all fit in, but it can be made to work by truncating the asset id:

Is it possible to display it on 2 lines rather than truncating it?
The reason is that it's better to expose scams in this view rather than having to clik into the asset page. Someone may create a phishy token with a domain that looks very similar to the original, the only thing that can't be duplicated is the full HEX ID

[shesek]

The reason is that it's better to expose scams in this view rather than having to clik into the asset page.

Even when truncated, you can still see the first 35 characters, or about 17 bytes. Finding a collision for this is not very realistic -- or, at the very least, that kind of hashing power would be better spent on mining bitcoins than on phishing. Also, I think users are probably more like to visually verify using the domain name than using the asset id.

But in any case, I went ahead and changed it to display the full asset id (in 67ecc41). Let me know if you prefer to go back to truncating.