Skip to main content

​
Store Listing Fields

When you register an app, you provide metadata that appears in the app store:
FieldRequiredDescription
NameYesDisplay name for your app
DescriptionYesShort summary shown on the store card
LogoYesSquare image for the app icon
CategoryYesFocus, Gaming, Wellness, or Research
WebsiteNoExternal link to your app
Social linksNoTwitter, Discord, GitHub, etc.
Team membersNoPublic team display

​
NFT Metadata Standard

App tokens and in-app items follow ERC-721 with ERC-4906 metadata update signaling. This means metadata changes emit on-chain events that marketplaces can listen to for auto-refresh. Example metadata JSON: 
{
  "name": "My Elata App Token",
  "description": "Access token for the My App ecosystem",
  "image": "ipfs://QmExample.../logo.png",
  "external_url": "https://myapp.example.com",
  "attributes": [
    { "trait_type": "Category", "value": "Gaming" },
    { "trait_type": "Version", "value": "1.0" }
  ]
}

​
Image Requirements

AssetRecommended SizeFormat
App logo500x500pxPNG or SVG
Token image1000x1000pxPNG
Store banner1200x630pxPNG or WebP
Use square images for logos and token images. Non-square images will be cropped in the store.

​
Storage Options

OptionBest ForNotes
IPFS (Pinata, NFT.Storage)ProductionRecommended. Decentralized and permanent.
ArweaveProductionAlternative permanent storage.
Centralized HTTPDevelopmentFine for testing. Do not use for production tokens.
Once metadata is referenced on-chain, changing the underlying content at the same URI does not trigger an ERC-4906 update. Use setTokenURI to point to new content and emit the update event.

​
Updating Metadata

After launch, your Safe can update app metadata by calling the appropriate registry function. Token metadata updates follow the ERC-4906 pattern: set a new URI and emit the MetadataUpdate event so marketplaces and indexers refresh.

​
Next

Launch Your App

Deploy your app on-chain

Post-Launch Checklist

What to do after launch

Items and Unlocks

Create in-app items