Enhancing CIP25 Standard

[davestaxcp]

with the initial publishing of CIP25, a new organizational example was set to include data into descriptions to further respresent tokens using counterparty

https://github.com/CounterpartyXCP/CIPs/blob/master/cip-archive/cip-0025.md

linking meta-data to the token started off mainly linking to domain hosted pictures, json files or jsons with hashs. This owned domain based theory was used by various organizations, businesses, companies (etc) on counterparty and is still somewhat common since 2014.

what became a 'standard' in the later years 2016-2018 by normal users was linking to more 'community' sources like imgur, soundcloud, youtube etc.

but many of those links died, and much of the art, content and purpose of many old projects was lost.

---

because of this issue, users and organizations alike have used other methods to link their data to tokens.

IPFS, STAMPS, Ordinals and flat Base64 broadcasts to name a few main examples, but the overwhelming majority seems to lean into JSONs published to the Arweave blockchain.

There are many reasons for this (easy, cheap, fast)... but most importantly because of a website called easyasset.art
(video tutorial by RobotLoveCoffee https://www.youtube.com/watch?v=pENROu4fCTE)

which was created by key community members and remains an automated 'take a penny leave a penny' situation.

and it is not like individuals can't do the process themselves (video tutorial by RobotLoveCoffee https://www.youtube.com/watch?v=Ml6Qrz_GDnI).... but easyasset really is that easy.

---

which brings us to our present moment.

the JSON scheme introduced by Jdog in CIP25 has become the main 'example' for easy asset to create JSONs on Arweave

https://github.com/CounterpartyXCP/CIPs/blob/master/cip-archive/cip-0025/spec-v2.0.0-example.json

this includes things like:

the showing (and interaction) of custom content:

images:

videos:

as well as information the user chooses to provide as well as where these elements are stored (or sometimes 'inscribed'):

... my main point here for block explorers and infrastructure providers is that the counterparty community is very used to:

1. having all elements of our creations shown on the explorers
2. (bonus) having the elements of our creations shown in wallets!

the reason I say that is because I simply want to state there are some explorers out there that don't support all of these elements (and I am sure there are many more from the CIP25 schema i missed)

for instance TokenScan doesnt show OLGA STAMPS, and Horizon previously didnt show some CIP25 details.

to each block explorer their own, but the more you include, the happier users will be.

---

I think since 2022 when CIP25 was published there are a couple more indicators I think could be added that users have started to experiment with.

• for example some Fake Rare submissions have Augmented Reality art that links with apps
• some tokens have token gated access within their arweave inscribed html systems
• any more examples you can think of?

I think indicating newer versions of content in the CIP25 form is reasonable. It is very important to be 'backwards compatible' so all earlier tokens show correctly as well.

Since CIP25 the only new JSON standard proposed has been Adam K's 'Horizon Token Standard':
#142

This new style (as mentioned by Adam in a recent Counterparty Community Space), is intended to be an extension of CIP25 to keep it backwards compatible for block explorers but the newer json style leans into... (as described by Grok):

---

keep in mind there is an important element here with enhanced asset info that needs to be enforced by block explorers:

"Sanitisation — Before rendering, clients MUST sanitise any payload whose content_type is executable or could embed scripts (e.g. SVG). A safe approach is to treat the file as opaque binary or use a strict SVG sanitiser."

How TokenScan shows this to users:

How xcp.io shows this:

---

lastly there is the element of new block explorer devs or infrastructure providers need a basis on where to start for categorizing of the most seen elements of the community, the old 'green banner' from TokenScan

I won't touch on it much as I have written about this here and continue to try to hunt down a conglomerate list of all recognized HNFT collections on counterparty:

#150

---

to conclude this topic I ask the community for their feedback on what should be added to the CIP25 schema, what is important to users and the community for the purpose of having a newer updated starting place for "the next EasyAsset or TokenScan" devs