Assets, eligibility and issuer controls

JOLT is asset 0. Other native assets have distinct registration, supply and issuer-policy records. A token adapter exposes their common-ledger balances to Solidity.

Asset registration

The registration service at 0x1022 supports fixed-supply assets and capped issuance under a separate mint committee. Authority rotation is versioned; renunciation is irrevocable and burns are holder-directed. These paths do not mint JOLT.

Asset IDs and active adapter addresses are configuration/state, not guessed constants. Privileged native-ledger adapter access requires admitted runtime code and the registered identity. Rotation closes new exposure through retired token identities while preserving the profile's exit routes.

Holder permissions and issuer holds

For a non-JOLT asset, the configured issuer committee can manage holder permissions, place expiring amount-specific incident holds, and delist/relist its asset. It cannot act on JOLT or another asset. A hold constrains an amount without transferring it to the issuer.

Delisting prevents new market exposure through the relevant AMM/farm/spot/quote/lending paths. Existing balances remain transferable subject to their other restrictions, and supported positions can exit.

Runtime eligibility

Genesis can enable code eligibility. An explicit code-admission committee admits/revokes runtime hashes for future deployment; factories and delegated execution must follow the configured rules. Revocation is not a power to replace already deployed code or arbitrary state.

Wallet source verification and screening are separate. A wallet override cannot bypass consensus eligibility, asset policy, locks or energy.

Not a bridge or identity registry

Bridge authority remains a proposal. Identity/private-record features are parked node scope. Asset permissions should not be described as a complete KYC product or proof of an external claim's legal validity.