Flipstarter for Token Icons. Would you Donate?

The Permissionless Software Foundation had our bi-weekly Community Committee meeting, and we talked about Flipstarter. This list of undelivered Flipstarters caught my eye, because it points to a clear lack of accountability in some Flipstarter projects. The PSF has a mature system in place to track accountability, and I thought there might be a natural fit between the two. I wanted to bring it up and discuss it with the PSF community and so we did that in yesterdays meeting.

One of the results of this discussion was the idea of starting a Flipstarter to build an implementation of this mutable data specification for tokens. Among other things, this would allow SLP token creators to specify an icon for their token, and wallets could detect these token icons automatically. This could all be done permissionlessly and automatically, and as an added bonus, the token creator could change the icon at any time in the future (rebrand).

That specification represents a big improvement over the current state of token icons, which seems to be a hair-on-fire problem for the SLP token community right now. There are multiple people every day in the SLP Telegram channels asking how to get an icon attached to their token and have it appear in a wallet.

The PSF could build a JavaScript npm library to help other wallet developers integrate this protocol for token icons into their own wallet, and we could implement it into wallet.fullstack.cash, which is an open source, MIT-licensed web wallet that anyone can fork an use for their own business idea.

Before we go to all the trouble to launch a campaign though, I wanted to put the question out to the community:

• Is this something you're interested in? Would you donate to the development via Flipstarter?

Many wallets in the ecosystem are not based on JavaScript, so they wouldn't be able to directly consume a library we could produce. But I think having it encoded in any language and proving that it works would help every wallet developer.

This mutable data spec goes far beyond just token icons. They would be a way to track a changing video-game character over time with a token. An NFT representing artwork could track the history of that piece of art. There are a ton of additional applications for this specification. Token icons are just the tip of the iceberg.

I had a hand in the creation of the SLP implementation, and since it's creation, I've watched the industry struggle with a good way to implement a trustless, permissionless way to implement icons. This is it. Does it interest you?