# B20X Protocol Scope

B20X is an early BSC launch memory layer. It helps turn a BSC token launch into a signed, indexed B20-concept launch packet.

B20X follows a simple operating model:

```text
BSC settles the token.
BEP-20 moves the token.
B20X records the launch.
```

## What B20X Is

- A BSC-only launchpad and launch registry.
- A B20-concept application layer for creator-signed launch packets.
- A public CA visibility surface for tokens created through the supported B20X flow.
- A local-signer workflow: the creator signs from their own wallet; the site does not receive the private key.
- A registry/index layer that joins creator wallet, token metadata, CA, scanner state, and launch evidence.

## What B20X Is Not

- Not an official Base B20 implementation.
- Not a chain-level standard on BSC.
- Not a replacement for BEP-20.
- Not a guarantee that a token is safe, profitable, liquid, or official.
- Not a custody service.
- Not a place to paste private keys.

## Registry Admission State

Launch records appear only after a supported admission path is complete. A record may be absent when the registry is waiting for creator-wallet sync, BSC route discovery, or pinned snapshot verification.

The registry rule is:

```text
The registry starts empty by design. A launch appears only after creator-wallet sync, BSC discovery, or pinned CA verification.
```

## What Gets Verified

The registry can verify public facts:

- chain id is BSC `56`
- a creator wallet signed the B20X sync message
- the CA exists on BSC
- the CA can be linked to an allowed launch route or pinned launch record
- token metadata can be read from public sources
- scanner state can be fetched where available

The registry cannot prove:

- future price performance
- whether a team will keep building
- whether liquidity will remain
- whether any unofficial CA is safe
- whether an external scanner is complete

## Official CA Policy

Until B20X publishes a formal announcement on the official website and X profile, any address claiming to be the official B20X token should be treated as unofficial.

The official channels are:

```text
Website: https://www.b20x.xyz
X:       https://x.com/b20x_bsc
```

Testing tokens may appear during development. They are not the official B20X token unless the official channels say so explicitly.

## Security Model

B20X separates local signing from public registry storage.

Users are responsible for:

- their local machine
- the SDK/source code they run
- the RPC endpoint they use
- the wallet they sign from
- the public registry/indexer policy
- the official communication channels

Users should reject:

- screenshots without CA links
- random CA posts in replies
- private-key requests
- unofficial "B20X official token" claims
- scanner badges as absolute safety guarantees

## Record Admission Flow

B20X records are admitted through visible public evidence.

1. Public docs explain the scope and trust boundary.
2. The local SDK can print the launch packet before signing.
3. A test wallet can run the flow with minimal BNB.
4. The creator wallet signs a B20X sync message.
5. The registry shows CA, signer, source, and scanner state.
6. The official channels publish the final CA when the official token is live.

The goal is a consistent launch record: local intent, BSC execution, registry visibility, and official-channel publication.