Unread0Awaiting review
Notifications
Stay updated on your token launches, configuration readiness, and ecosystem alerts.
Alerts0Action needed
Updates0Project progress
System0Platform notices
Projects
Create, manage, and track all your token launches.
Total0All projects
In progress0Active builds
Ready0Can deploy
Deployed0On Mainnet
| Project | Status | Progress | Updated |
|---|
No projects match this filter.
+
Create new token project
Start a fresh UNR-20 configuration without losing deployed tokens.
Launch checklist
Work through the steps above — status updates as you edit each area.
Distribution preview
Token deployed successfully.
Token Details
Identity, branding and metadata that holders will see on explorers and wallets.
PNG, JPG, SVG • Max 2MB
Logo appears on Explorer, wallets, and the Projects table.
2–32 characters. Shown on Explorer and wallets.
2–8 characters. Tickers are case-sensitive in wallets. Keep it unique on Unara.
Supply & Distribution
Cap the token, choose mint/burn behavior, and map genesis allocations.
Initial supply1,000,000,000UNA
Community40%Largest bucket
Treasury + team35%Should vest
Allocation total100%Must equal 100
Supply mode
UNA
Genesis allocations
Each bucket should have a receiving wallet. Team, advisor and treasury usually vest before public trading.
Permissions
Who can mint, pause, blacklist, or transfer ownership after deploy.
Transferable ownership
Allow the deployer to transfer contract ownership after launch. Prefer a Vault or multisig.
Pausable transfers
Owner can pause transfers during an emergency. Markets treat permanent pause rights as higher risk.
Blacklist / allowlist
Restrict transfers to sanctioned or approved addresses. Keep the list narrowly scoped.
On-chain metadata
Store name, symbol and logo URI in the contract so Explorer stays in sync.
Owner key should live in Unara Vault, not a hot wallet.
Review & Deploy
Confirm parameters, estimate gas, then sign with the runtime wallet.
NetworkUnara MainnetChain ID 721
Est. cost~12.5 UNAToken factory fee
Time~30sAfter signature
StatusDraftChecks pending
Launch gaps
Vesting Schedules
Lock team, advisor and treasury tokens on a cliff + linear unlock.
Preview
Cliff6 months • 0% unlocked
ThenLinear over 24 months
Fully unlockedMonth 30
Each schedule deploys as a companion vault and receives that bucket at genesis.
Scheduled buckets
Taxes & Fees
Optional transfer taxes routed to treasury, liquidity or burn.
Enable transfer tax
Deduct a percentage on each transfer after launch.
Combined tax: 0%
Unara listings prefer taxes at or below 5% combined. High taxes can block DEX routers.
Combined tax is above 5%. Some DEX routers may refuse the pair.
Mint / Burn Rules
Cap future inflation and define who may destroy supply.
Supply mode is Fixed. Mint controls stay off unless you switch to Mintable.
Hard max supply
Even if mintable, never exceed this cap.
Holder burn
Any holder can burn their own balance.
Owner burn-from
Owner can burn from any address (high trust assumption).
Snapshots
Capture holder balances at a block for airdrops, governance or claims.
| Name | Block | Min | Status |
|---|
No snapshots yet. Drafts stay local until the token is deployed.
Documentation
How Token Forge maps onto Unara token launches.
Launch in four steps
Token Forge is a local launch desk for UNR-20 tokens. Work left-to-right: identity, supply, permissions, then review. Advanced modules attach at deploy if you enable them.
- Token Details — name, ticker, decimals, logo, description and socials.
- Supply & Distribution — cap, mint/burn mode, and genesis buckets that must total 100%.
- Permissions — owner transfer, pause, lists, and on-chain metadata.
- Review & Deploy — checklist, wallet signature, factory deploy (simulated in this build).
The Overview wizard is the same draft. Sidebar pages edit the same saved configuration.
Runtime wallet and signing
Connect Runtime Wallet uses the same Unara runtime session as NFT Studio. The connected address pays the factory fee (~12.5 UNA on Mainnet, chain ID 721) and becomes the default owner unless you set another owner wallet.
- Deploy is blocked until a wallet is connected.
- Genesis transfers go to the wallets you enter on each allocation bucket.
- Keep mint and owner keys in Unara Vault after launch — not on the hot signer.
This desktop build simulates connect and deploy. A later pass can submit the same draft to the live factory.
Allocation and vesting
Genesis supply is split across Community, Treasury, Team, Ecosystem and Advisors. Each row needs a percentage and a receiving wallet. The token amount is derived from total supply.
- Totals must equal 100% or Review will block deploy.
- Team, advisor and treasury should usually sit behind a vesting vault.
- A schedule is cliff months, then linear unlock. Default Team is 6 + 24 (fully unlocked at month 30).
- Revocable schedules let the owner claw back unvested tokens — document that if you enable it.
Taxes, listings and DEX routers
Transfer tax is off by default. If you enable it, buy / sell / P2P percentages are taken on each transfer and sent to the tax recipient.
- Unara listings prefer a combined tax at or below 5%.
- Above 5%, some DEX routers refuse to pair the token.
- A recipient wallet is required whenever tax is on.
- Tax settings appear on the Review checklist so you can confirm them before signing.
Security checklist
Forge will not replace a review, but these items stop the most common launch mistakes.
- Put ownership on a Vault or multisig. Do not leave mint on a browser wallet.
- Vest insider allocations before public trading.
- Avoid owner burn-from unless you have a stated compliance reason.
- Keep pause rights temporary and publish the policy.
- Keep taxes low enough for routers. Verify source on Explorer after deploy.
After deploy
When the factory confirms, Explorer indexes name, symbol, supply and logo. Your draft stores the token address locally so refresh still shows the deployed state.
- Move owner and treasury keys into Unara Vault.
- Snapshot drafts become “Ready to run” after deploy (still local in this build).
- Use New draft to start another token without losing the record of the last address until you overwrite.
Token Standards
Forge deploys Unara-compatible fungible tokens with optional modules.
UNR-20 Fungible
Default Token Forge output. Name, symbol, decimals, transfer and approve — the surface Unara wallets and DEX routers expect.
| Surface | Type | Notes |
|---|---|---|
| transfer / transferFrom | Method | Moves balances; tax hook may wrap these. |
| approve / allowance | Method | Required for routers and Vault. |
| balanceOf / totalSupply | View | Explorer and wallets poll these. |
| Transfer / Approval | Event | Indexed by Explorer for holders. |
Mintable / Burnable
Optional roles for inflation and deflation. A hard cap can stay immutable even when mint is enabled.
| Forge control | Extension | Default |
|---|---|---|
| Supply mode Mintable | mint(to, amount) | Off (Fixed) |
| Hard max supply | cap check on mint | On when mintable |
| Holder burn | burn(amount) | On for burnable modes |
| Owner burn-from | burnFrom(account, amount) | Off |
| Additional minters | MINTER_ROLE | Empty |
Vesting vault
Companion contract per schedule. It receives that bucket at genesis and streams unlocked tokens after the cliff.
- Cliff: 0% unlocked.
- Then linear over the duration.
- Fully unlocked at cliff + duration.
- Revocable: owner can return unvested tokens to treasury.
Tax module
Hook-based transfer fees. Disabled by default so listings stay simple. When on, buy / sell / P2P each take a percentage to the recipient wallet.
Combined tax above 5% is flagged in Forge and may break Unara DEX routers.
Compatibility
UNR-20 tokens from Forge are meant to work with the rest of the Unara desktop:
- Runtime wallet — deploy + genesis transfers.
- Unara Explorer — name, symbol, holders, verified source.
- Unara Vault — custody owner, treasury and tax keys.
- DEX routers — require approve and low or zero tax.
Editing
Unara Token
0%
Complete each step below to reach deploy.
