Build With Us
This community program is being shaped now. The goal is to bring token designers, artists, engineers, communities, and launch partners together around new token types.
Mirage Garden wants to be a home for people building beyond the default token playbook. That includes ERC tokens, experimental non-ERC tokens, token-linked objects, community launch mechanics, and tools that make unusual token systems easier to understand, share, and grow.
The next community surface is not just a chat or announcement feed. It is meant to become a builder network for launching, testing, popularizing, and supporting new token formats.
What we want to support
| Builder need | Mirage direction |
|---|---|
| ERC token communities | Launch and distribute tokens with clearer object, marketplace, and community layers |
| Non-ERC experiments | Give custom ledgers and token-like systems a public place to be discovered |
| soToken projects | Help creators use LOA and BOA mechanics without needing to explain the whole protocol from scratch |
| Partner sites | Let teams launch through Mirage APIs from their own website |
| Early communities | Reduce launch friction and fees so experiments can start smaller and grow in public |
Why community matters
New token types usually fail before people can understand them. The contract may work, but the surrounding pieces are missing:
- a simple way to explain the token type
- a launch path that does not require users to leave the project site
- public docs and examples that make the mechanics legible
- creator and holder support after launch
- distribution tools that do not punish small experiments with high fees
Mirage Garden is being built to sit around those gaps. We want builders to have a place where a token can be launched, explained, traded, extended, and supported as a living community object.
Launching from your own site
The planned Mirage API direction is simple: projects should be able to use Mirage infrastructure without giving up their own front door.
That means a community could eventually:
- keep its launch on its own website
- call Mirage APIs for token or object creation
- use Mirage indexing and discovery surfaces
- route users into Mirage marketplace and profile tools when useful
- qualify for heavily reduced fees when launching through supported community flows
The intent is not to force every project into one branded launch page. The intent is to make Mirage a reliable launch layer that communities can embed, extend, and make their own.
ERC and non-ERC token types
ERC standards matter because wallets, exchanges, and apps know how to read them. Non-ERC experiments matter because some of the best token ideas do not fit inside an existing standard yet.
Mirage Garden wants to support both paths:
- ERC-compatible tokens that benefit from familiar infrastructure
- custom token ledgers that need better public interfaces
- token-linked object models like LOA and BOA
- hybrid launches where an ERC token powers a richer object or state layer
- future token types that need documentation, tooling, and community review before they become common
The regular ERC-20 foundry is the first step outside the native LOA/BOA launch flow. Extended NFT support is planned separately because several standards, including token-bound accounts and rental-style user roles, are currently NFT-centered.
How to get involved
This page will become the entry point for community launches, API access, partner site integrations, builder support, and reduced-fee launch programs.
For now, the program is coming soon. The direction is clear: bring builders together, help them launch new token types, and make Mirage Garden a place where those tokens can become understandable, useful, and visible.