Skip to documentation
Resources/Docs
MarketsSinjoh v2

Tokens & settlement

Fixed-supply clones, metadata, transfer rules and PoolManager claim accounting.

2 min read·
On this page

Fixed token identity

Launch tokens and market vaults are ERC-1167 clones initialized atomically. The implementation initializer is disabled, and an existing clone has no upgrade path. A newly approved hook/version does not replace an older token’s code or pool.

A launch token starts with its fixed supply and supports holder burns and bounded creator metadata edits. New implementations expose Pons-compatible getTokenInfo(): creator, logo, description and a socials tuple containing Twitter, Telegram, Discord, website and Farcaster. The SDK also supports the original flat return layout. Native tokens start Pre-Bonded and permanently become Graduated when their indexed USD market cap first reaches $40,000. The existing token of a migrated market retains its own original contract and interfaces.

Ordinary transfers and outside-pool detection

Ordinary ERC-20 transfers do not pay Sinjoh market taxes. For launch tokens, a recipient detector rejects pools belonging to listed blocked v2/v3/Slipstream factories only after checking their claimed factory, token identities and canonical pool identity. A bounded factory read and versioned cache keep detection work controlled.

Adding a blocked factory invalidates prior recipient-cache decisions under the new list version. This mechanism recognizes the specified pool families; it is not a universal detector for every possible trading contract. Migrated unchanged tokens do not acquire this detector.

PoolManager exit authorization

Launch-token exits from an unlocked PoolManager require a bounded transient authorization from a trusted hook. The authorization is consumed by the actual transfer, including legitimate trade output, internal destruction and refunds of unused prepaid input. It is not a permanent arbitrary-spend allowance.

Transfers into PoolManager remain possible. Legitimate locked-PoolManager exits, including protocol-fee collection, are permitted while recipient checks still apply. When the backing itself is a gated Sinjoh token, its backing-side movement needs compatible authorization too.

ERC-20 balances and ERC-6909 claims

PoolManager can hold token/backing balances as ERC-6909 claims. Fee buckets and deferred floor-bought tokens have specific internal accounts. Claims held for ordinary holders still count toward relevant holder obligations; a wallet-only ERC-20 balance sum is incomplete.

Floor-bought launch-token claims are excluded from holder obligations and market-cap supply before deferred destruction. Burning them later must not subtract them twice. A migrated-token transfer to the dead address is different: it does not reduce that token’s ERC-20 total supply. The lens exposes the applicable supply categories for each market.