Glossary

A-C

Active capacity

The number of soToken objects a wallet can actively support from live token balance.

Balance record

The factual record of an object birth: original minter, birth block, token balance, interval, and birth path/context.

BOA

Bound Object Asset. The stricter bound-object class that includes UniPeg-style behavior, AGENTZ v1.0.1, and similar balance-bound designs. In v1.2, BOAs can unbind, burn, or attempt auto-follow when token support is lost.

AGENTZ v1.0.1

An older Mirage-compatible BOA collection. It remains supported in the app, but new public launches should use v1.2 LOA/BOA/soToken language.

Claim

The action that births object IDs from live token support capacity. Claiming does not spend the token.

D-M

Dormant

The LOA state used when an object remains assigned to a wallet but does not currently have enough token support to be active.

D-M

Interval

The amount of token required to support one active object slot.

LOA

Liquid Object Asset. Mirage Garden's main v1.2 soToken path. A LOA object goes dormant instead of being lost when token support drops.

Object ledger

The custom ledger that tracks specific object IDs, owners, approvals, birth records, and object state.

N-Z

soToken

Synthetic Object Token. A liquid or semi-liquid token system with an on-chain object layer bound to token ownership, balance, or state.

Source token

The ERC-20-compatible token whose balance supports object capacity.

Supported count

floor(sourceToken.balanceOf(owner) / interval).

Sync

The reconciliation action that updates object state against live token balance. LOAs become dormant or active; BOAs unbind, burn, or attempt auto-follow depending on launch policy.

transferObject

The Mirage-native v1.2 transfer function for moving a specific object plus exactly one token interval.

vBundle

A future or historical vault-backed bundle idea. It is not the current LOA standard.