Ecosystem

Two ecosystem assets in two distinct environments: KCSC under user custody on Base, and wKCSC mapped inside the KCSC account.

On-chain assetKCSC

The Base-native ecosystem asset held and managed by users in their own wallets.

Account assetwKCSC

A mapped ecosystem asset recorded inside the KCSC account for KCSC-related product capabilities.

Two asset roles

On-chain ownership. Account-side utility.

The two assets share an ecosystem context while retaining separate records and responsibilities.

KCSC on Base

KCSC exists on-chain. Wallet custody, network transfers, and transaction records remain with the user and the Base network.

wKCSC in the account

wKCSC exists in the KCSC account as a mapped asset for supported platform modules and account-side utility.

A clear boundary

On-chain KCSC and account-side wKCSC remain distinct unless a confirmed product capability explicitly connects them.

Asset relationship

One ecosystem, two distinct ledgers.

The asset name and environment make it clear where ownership is recorded and which product rules apply.

01

Hold KCSC on-chain

KCSC remains in a user-controlled Base wallet and follows the public network record.

02

Recognize wKCSC in the account

wKCSC is recorded by the KCSC account and follows the rules of supported platform capabilities.

03

Keep the records separate

A wallet balance and an account balance are different records and should not be treated as interchangeable by default.

04

Follow confirmed utility

Current wKCSC capabilities and any connection to KCSC are presented only when the relevant product module is confirmed.