Introduction
soTokens, object ledgers, and token-first launches on Base
Mirage Garden documents LOA and BOA soTokens: ERC-20-compatible token systems with an on-chain object layer tied to live token balance, ownership, or state.
LOA
Liquid Object Asset. The token stays liquid; unsupported objects go dormant and reactivate when balance support returns.
BOA
Bound Object Asset. The stricter bound-object path where unsupported objects can unbind or burn.
Mirage Garden is the home for soTokens on Base: liquid or semi-liquid token systems with an on-chain object layer bound to token ownership, balance, or state.
The current v1.2 protocol introduces two soToken classes:
- LOA: Liquid Object Asset. The token stays liquid; unsupported objects go dormant and reactivate when balance support returns.
- BOA: Bound Object Asset. The stricter bound-object style where unsupported objects can be unbound or burned.
The protocol is not an ERC-721 mint-gate. A creator chooses a token, an interval, a max object count, media rules, and object behavior. A wallet supports:
floor(sourceToken.balanceOf(wallet) / interval)
active object slots. Specific object transfers move the chosen object ID plus exactly one configured token interval.
New readers should start with soTokens, then LOA, BOA, and the Contract Reference.
Current status
| Track | Status | Meaning |
|---|---|---|
| LOA | v1.2 | Main going-forward path: liquid token, dormant object state |
| BOA | v1.2 | Bound Object Asset |
| PixelCats | v0.8 proto-BOA | Historical Mirage-compatible collection preserved in Discover |
| AGENTZ | v1.0.1 BOA | Older BOA collection preserved in Discover |
What these docs cover
| Section | Purpose |
|---|---|
| soTokens | Parent category for LOAs and BOAs |
| LOA | Liquid Object Asset behavior |
| BOA | Bound Object Asset behavior |
| Birth Records | Balance records, seeds, and historical records |
| Glossary | Definitions for soToken, LOA, BOA, interval, and sync |
| Launch a soToken | Creator route for LOA/BOA launches |
| Claim an Object | Collector claim, sync, and transfer flow |
| Marketplace | LOA/BOA listing and purchase behavior |
| Contract Reference | Current Base and Base Sepolia contract addresses |
| ClankerCats Origin | PixelCats as the proto-BOA/uPEG-like precedent |
| Build With Us | Coming soon community program for ERC, non-ERC, and API-powered launches |
Public links
- Homepage: mirage.garden
- App and marketplace: app.mirage.garden
- Launch routing: app.mirage.garden/launch
- PixelCats market: app.mirage.garden/market/pixelcats
- Public contracts: github.com/Mirage-Garden/basePeg
Documentation rule
Do not call ERC-721 token-gated mints "soTokens." Proper soToken behavior means:
live token balance creates active object capacity
unsupported LOA objects become dormant instead of destroyed
BOA lost-support behavior is explicit at launch
specific object transfer moves object + one token interval