coral-xyz / xnft Goto Github PK

@armaniferrante currently the symbol of an xNFT is defined by name.slice(0, 3).toUppercase().

should this be a separate input for the publisher to define a custom symbol or is this more of a technicality for utilizing Metaplex metadata accounts?

e.g. can use a *

This table should only have one entry, App, atm. Tables and images have been punted. See https://github.com/coral-xyz/xnft/blob/master/programs/xnft/src/lib.rs#L509. And any other places inside the app that use it.

Add program update instruction and update the website to support the update action.

currently it just asks for a new url rather than allowing one to upload a totally new url/blob

If you upload a new xNFT and click home, it won't display without hard refreshing the page.

We should allow one to buy/sell xNFTs.

In a separate issue--not important to do now since we dont have any users--we should also limit the ability to update metadata to devs that are trusted.

Also need sybil resistance here

it should only be removed from the downloaded/installed section

as discussed in #85 , the current editing flow requires updating to be more storage platform agnostic wrt how updating the MPL account data is done.

As a user, I need to be able to download the mobile app and browser extension.

I should be able to discover an xNFT on the site and then open and try it out inside backpack without installing.

Add program uninstall instruction and update the website to support the uninstall action

We need a way to categorize them (e.g., games, defi, etc).

perhaps this isn't necessary since the account already has updated_ts value.

reported by gajesh

@aarongillett for design addition

mainly for the purpose of update detection. this could manifest in the form of:

• last update timestamp (current)
• bundle X byte hash
• semver
• etc.

This confused gajesh when he uploaded for the first time. We should make them consistent--either index.js or bundle.js (but not both).

we need a sybil mechanism for this

I had to refresh the page manually.

Might be worth punting this to when we have some type of live update stream in the future (or we can hack together a background poller).

Unclear if we want to allow this, but it would be useful.

It's not clear if it went through or not. Eventually the loading indicator stops and the "Free" button turns into an "Open" button, but we probably want something more obvious to signal success.