bPeg
Proper balance peg
A creator chooses a source token, interval, max object count, renderer, and seed module. A wallet can validly own no more objects than floor(sourceToken.balanceOf(wallet) / interval).
MIRAGE GARDEN
bPegs are balance-native objects
Mirage Garden is rebuilding bPeg around the uPEG/PixelCats-style primitive: live token balance creates object capacity, and a specific bPeg transfer moves the object plus one configured interval of the source token.
Specific send
Object plus interval
Normal ERC-20 transfers move fungible balance. Mirage-native bPeg transfers move a chosen object ID and exactly one source-token interval together.
ePEG
Existing-token route
Already-live ERC-20 communities can attach an external bPeg ledger. It works through Mirage-native claim, sync, transfer, and marketplace flows, with optional one-way ERC-721 receipt conversion.
What changed
The old Factory-era bPegs were token-gated ERC-721 birth records. That code is being preserved as nPEG-compatible foundation work, but it is not the true bPeg core. True bPegs do not depend on wallet/NFT marketplace compatibility; they are Mirage-native objects with their own ledger and transfer rules.
Seed and hook modules
Uniswap v4 hooks are one possible seed source, not the whole protocol. Projects can use default transaction seeds, Uniswap swap context, GameFi events, quests, social campaigns, or custom developer modules, as long as those modules cannot bypass balance capacity, sync, ownership, max supply, or object-plus-interval transfer semantics.
PEG taxonomy
bPegBalance-native object tied to live source-token intervals.
ePEGExternal-token bPeg rule for already-existing ERC-20 communities.
nPEGNFT-compatible birth record / ERC-721-style legacy or future route.
vPEGFuture vault-backed PEG where backing is deposited into a vault/object.