Deployment flow

This page describes what happens under the hood when you tap Review & Deploy in any Creator Studio factory.

1. Form validation

The factory screen validates required fields (name, supply, jurisdiction, etc.) before enabling deploy. Draft values stay in local state until you sign.

2. Metadata packaging

For RWAs and media NFTs, documents and images are packaged into metadata:

• Prospectus, valuation certificates, floor plans (P01)
• Audio/video cover art (P14, P15)
• Legal hashes referenced on-chain via IPFS CIDs

Status: uploading_metadata

3. Transaction construction

BlockchainDeploymentService builds the call:

Substrate (EmpoorioChain)

Proptech.registerProperty(...)
EmpRwa.tokenizeAsset(...)

EVM (Ethereum)

ERC-20 deploy via EooniaERC20.sol

The preview screen shows pallet index, call name, and estimated fee in DMS or ETH.

Status: signing_transaction

4. Local signing

Eoonia signs with your HD wallet keys inside encrypted Hive storage. Biometric or PIN unlock is required.

Status: broadcasting

5. Confirmation

The app polls for inclusion and finality. On success you receive:

• txHash — explorer link
• contractAddress or assetId — for My Protocols and Bazaar listing

Status: confirming → finalized

Failure modes

Symptom	Likely cause
failed: insufficient balance	Not enough test DMS — use faucet when available
failed: pallet not found	Runtime on testnet may lag docs — check release notes
Stuck on confirming	Network congestion — retry or lower priority
EVM deploy reverts	Wrong network selected — switch to Ethereum for P19

Testnet checklist

1. Network: EmpoorioChain testnet (wss://testnet.empooriochain.org)
2. Explorer: testnet.explorer.empooriochain.org
3. Integration tests: test/creator_studio_integration/pallets_connection_test.dart (in repo)

Next steps

• My Protocols — view deployed assets
• Real Estate example (P01)