Your application workspace.
A guided workspace for bundling, staging, signing, and deploying an ITZApp with its contracts.
ITZABuild
connectingBuild with confidence.
The workflow will bring the important steps into one place: ITZApp bundling, asset checks, Web Push setup, WASM contract compilation through Firexracker, staging previews, and deployment readiness.
Your build identity is ready for the guided workflow: package, compile, stage, review, and deploy with confidence.
What are you building?
Build, test, and launch your app on the ITZA blockchain. All the tools and steps you need will live here.
Name your project
Choose a name you will recognize in your build workspace.
My projects
No projects yet. Start your first project to see it here.
Select a cluster
Choose where this project will be developed and launched. Cluster details are read directly from the network.
Project
Project keys
Two wallets keep project storage and application operations separate.
Private keys stay in your browser by default. Imported or legacy project keys can optionally be saved online in encrypted form.
Production keys
* Designated rent wallet Funds deposited into a rent wallet cannot be withdrawn.
* Designated rent wallet Funds deposited into a rent wallet cannot be withdrawn.
Dev keys
* Designated rent wallet Funds deposited into a rent wallet cannot be withdrawn.
* Designated rent wallet Funds deposited into a rent wallet cannot be withdrawn.
Fund your project wallets
* Designated rent wallet Funds deposited into a rent wallet cannot be withdrawn.
* Designated rent wallet Funds deposited into a rent wallet cannot be withdrawn.
* Designated rent wallet Funds deposited into a rent wallet cannot be withdrawn.
You must fund your app contract if:
- You intend to register a domain name on your app (requires a payment).
- You intend to issue funds from your WASM contract (for example, granting a welcome credit).
You MUST fund your rent wallet sufficiently to cover rent for all uploaded assets. You will not be able to use functions in the Builder without funding this wallet.
All available project keys will be encrypted in your browser with your account login wallet and stored on the build service. Anyone signing in with this same account will have access to these keys and the project functions. The service receives only encrypted data, not readable private keys. Keep your own secure backup.
Turning this off removes keys from the current online cache, but cannot revoke copies already saved on another device.Give your application a memorable address.
Register a network-wide @application handle, a custom domain, or both.
Bring this application into the Builder
The imported app wallet already owns the identities below. They have been added to this project. You can migrate a domain to managed DNS, certificate automation, and cluster-wide SSL installation.
Custom domain
Connect a domain you purchased to cluster Not selected. We will verify DNS, register it on-chain, and guide the SSL setup.
Bring a domain you own.
You must purchase a domain name from a domain registrar before continuing. Enter it without www, a protocol, path, or port.
Point your registrar to ITZA Labs.
At your registrar, replace the domain’s authoritative nameservers with every name below. DNS changes may take time to propagate.
Point your domain to this cluster.
Create an A record for the bare domain, www, or both. At least one must resolve to an online node on cluster Not selected.
Automatic SSL for self-managed DNS
One authorization step is required. It uses the existing remove and re-register transactions to add the ITZA certificate-uploader key. Both transactions are inexpensive and run automatically after you approve. Certificates and their private key will be shared with every node serving this application.
Add both CNAME records at your DNS provider. Keep them permanently so renewals remain automatic.
Install your own certificate
Upload the issued certificate chain and its matching private key. A CSR is not a certificate and cannot be installed. You must return here and upload a replacement before every expiry.
DNS zone editor
Add mail, verification, and service records for your domain.
ITZA manages the apex and www A/AAAA records and the SSL challenge records. They cannot be changed here. You may add apex MX and TXT records for email, including SPF, DKIM and verification records.
@ for the bare domain, mail for mail., and selector._domainkey for DKIM.What does this application need?
Choose only what you plan to use. These choices configure the rest of the workspace.
Does your application require an alt-coin?
Describe the currency, derive its reproducible keys, generate its signed certificate, and mint it on the selected cluster.
This cluster does not support fiat exchange rate proposals.
Choose the currency certificate key and the separate wallet that will receive the minted funds. Both must be on this project's cluster and have no on-chain objects.
This cluster requires an altcoin proposal. Your altcoin must receive a majority vote before it can be used or activated. The majority vote must be received within 30 days of minting. Altcoin proposal voting is not yet implemented by the node.
Plan the token distribution
Work through the allocation and wallet rules first. Nothing is transferred or locked until you finalize the complete plan.
Storage Location and Cost
Choose which validators keep this project’s rented data and compare their per-epoch storage costs.
Your project’s current total cost
Calculating…
Choose required storage nodes
Required nodes remain fixed until you change this setting. Node-specific quotes apply to large hosted assets; contract, SQL, and social storage use the cluster price once.
Resilient extra copies
Extra validators are selected from nodes not required above. They are reassigned automatically when an assigned validator is no longer eligible.
Projected total cost per epoch
Cluster-priced objects, required-node asset quotes, and the estimated range for floating extra copies.
Storage locations can only be changed once per epoch (up to one hour). Nodes need time to coordinate, share your assets, and synchronize your desired locations. Changing locations is a time-consuming operation that cannot be repeated within the same epoch.
Egress costs and budget
Loading this cluster’s large-asset, contract-query, and WebSocket communication policy…
No budget loaded.These maximums apply per node, per epoch. An epoch can last up to one hour.
Calculated in the rent wallet’s currently selected payment currency. Actual spending depends on usage.
The budget belongs to this project’s rent wallet and becomes effective next epoch. It limits reimbursable use; it does not pre-purchase traffic.
Configure Push Notifications
Web staging workspace
Upload, organize, edit, and preview the exact files that will become your ITZApp.
Large-file assets
Files larger than 10 MB are stored separately and linked into HTML automatically.
Contract source, schema, and isolated build
Enable Smart Contract under Capabilities to unlock this workspace.
Cargo.toml and its locked package version without replacing your other settings.Zero-value contract execution fees prefer this currency. Altcoins require an active exchange policy and positive cluster-voted bias; otherwise the node safely falls back to ITZACoin.
Rust source
Create folders anywhere beneath contract/, including beside src/ for shared crates and browser WASM packages.
Additional browser WASM
Compile Rust packages alongside your contract. Each result is optimized and placed into your web app automatically.
SQL schema
The first schema is installed only with contract upload. Later schemas are marked pending and must add tables rather than replace existing ones.
Preparing isolated build…
Install this project on cluster
Build artifacts and web bundles are prepared by the staging service. Transaction payloads return to this browser, where your app and rent keys sign them locally.
Preserve a release, or continue from an earlier one.
The writable web and WASM workspace is always the current version. The first saved version is a complete baseline; later versions retain only changed files while remaining fully browsable and restorable.
Older versions
Expand a version to browse changed, unchanged, and deleted files in read-only mode.
Publish your application
Create the app-list entry users will see after installation.
Contract usage and cost projections
See actual execution traffic, then estimate the next three epochs using today’s cluster price.
Executions by epoch
Up to the 20 most recent execution counters stored in the contract wallet.
Next three epochs
Projection based on the execution history available above.
Manage this project
Change how this project is identified in Builder, inspect separately hosted assets and active rent storage, or remove it from Builder and the cluster.
Explore assets uploaded separately for this ITZAppReview separately hosted files
Large front-end files are stored on-chain outside the web container. Delete every asset here before removing the app from its cluster.
View all active rent costs for this appLoading rent records…Expand for individual items
These are the active on-chain storage records currently charged to this project’s rent wallet.
Remove items or retire app
Each action below is independent. You can remove names, the cluster application, or the Builder project without first removing the other components.
Names and domainsCheck registered names
For a managed domain, remove only its blockchain registration, only its managed DNS service, or both. Removing DNS service deletes the zone from every configured authoritative nameserver.
Remove app from clusterContainer and WASM only
Delete the front-end container and WASM contract from the main app wallet. Names, domains, separately uploaded large assets, and Builder files are left in place.
If you also want to remove the large assets, you must remove them from the list of assets above.
Remove app from BuilderCluster application remains online
Delete this project’s Builder record, staged files, WASM source, snapshots, and retained build results. Nothing on the cluster is removed.
Delete allComplete project cleanup
Delete every separately uploaded large asset, unregister all domains and @social names, remove the app container and WASM contract, remove any public app-list entry, and finally delete the Builder project.
Preparing…
Project activity
Review web requests and WASM activity recorded by the RPC nodes serving this project's rent wallet.
Confirming whether Builder can read this project's protected logs.
Validator-hosted agent capacity
Fund a project wallet
Choose the source of the funds below. Private keys stay in this browser and are used only to sign the transfer.
Only funded, spendable wallets appear. Rent and locked wallets can never be used as a source.
Enter an amount to see its smallest-unit value.