Connect a wallet to enable actions.
NFT settings
Paste metadata + image URLs. Configure supply and mint price as needed.
Shown as the NFT/collection name in wallets and explorers.
Short ticker, e.g. OMOMH. Set before deploy (cannot change later).
No trailing / → same metadata for all tokens.
Trailing / → folder style baseURI + tokenId.
Should match the image field in your metadata JSON.
Deploy fee ($1.99)
Paid in OCTA to the official OMOM minter. Amount from live OCTA/USD rate.
Recipient: 0xE2b3De60118290373CAf08f361041955E0d4C338
Deploy
Pays fee, then deploys. You become the contract owner.
Public Mint
Mint when the collection is open. Gas + mint price paid in OCTA.
Total: — OCTA
Owner Admin
Only the contract owner can use these controls.
Load a contract first.
Mint status
Mint price (OCTA)
Max per wallet
Base URI
Owner mint
Withdraw OCTA
Contract balance: —
How to use OMOM NFT Studio
- Connect wallet → OctaSpace (Chain ID 800001).
- Set max supply, max per wallet, mint price.
- Paste metadata URL + image URL → Check metadata.
- Deploy → pay fee → enable mint → mint.
Metadata example (HTTPS or IPFS)
Folder on IPFS or any HTTPS host:
├── 1
├── 2
└── ...
// File "1" JSON:
{
"name": "Octamom #1",
"description": "OMOM family NFT on OctaSpace.",
"image": "https://ipfs.io/ipfs/bafybeigYourImageCID/1.png",
"attributes": [
{ "trait_type": "Collection", "value": "OMOM" }
]
}
// Recommended base URI (HTTPS gateway — works in most wallets/browsers):
https://ipfs.io/ipfs/bafybeigYourFolderCID/
// Also valid:
ipfs://bafybeigYourFolderCID/
https://yourdomain.com/metadata/
HTTPS is often easier for wallets and browsers. You can still host files on IPFS and point
baseURI at a gateway like https://ipfs.io/ipfs/<CID>/.
Test: open https://ipfs.io/ipfs/<CID>/1 in a browser.
Network
- RPC:
https://rpc.octa.space - Chain ID:
800001 - Explorer: scan.octa.space