MINTING / METADATA
Make your token recognizable.
Permanent image and metadata documents for a Floor1 launch.
A mint references metadata stored on Arweave. Prepare the image first, then upload a JSON document that references it. Metadata storage and uploads are handled by your uploader, outside the SDK.
Document format
JSON
{
"name": "Floor Frog",
"symbol": "FROG",
"description": "A frog with a floor.",
"image": "ar://<image-transaction-id>",
"links": {
"website": "https://example.com",
"x": "https://x.com/example",
"telegram": "https://t.me/example"
}
}| Property | Meaning |
|---|---|
| name / symbol | Match the name and ticker passed to mint. |
| description | Token description; keep it within 500 characters. |
| image | ar:// URI of the uploaded image. |
| links.website | Optional HTTPS URL. |
| links.x | Optional HTTPS link on x.com or twitter.com. |
| links.telegram | Optional HTTPS link on t.me. |
Arweave URIs
Arweave transaction IDs contain 43 URL-safe characters: letters, numbers, underscores, or hyphens. Prefix the ID with ar:// when passing metadataUri to mint. Replace all example placeholders with real uploaded transaction IDs.
Verify before minting
Check that both uploads resolve through an Arweave gateway and that the JSON references the intended image. Permanent uploads are not edited in place. The SDK validates the URI shape, while the uploader and gateway handle upload confirmation and availability.