# PLAIS Mainnet Operational Policy

## Status

The canonical PLAIS Besu QBFT mainnet is technically operational. This policy is not an investment document, exchange-listing guarantee, public token sale document, or authorization to unlock public transfers.

Technical preconditions passed 11/11 on 2026-08-04. The network remains in `AWAITING_EXPLICIT_LAUNCH_APPROVAL`: public RPC, external deposits and withdrawals, operator signing, multichain transfers, validator key delivery, and automatic client rollout remain locked until their separate security, legal, custody, disclosure, and integration gates are satisfied.

## Mainnet Decision Principle

Public activation of PLAIS mainnet must be treated as a separate approval milestone, not an automatic consequence of technical network operation. Testnet operation, wallet testing, internal points, and simulated rewards do not guarantee allocation, conversion, exchange support, or public transfer access.

Mainnet may proceed only if all of the following are true:

- Technical stability is proven on testnet.
- Reward abuse controls are operational.
- Validator and node policies are enforceable.
- Wallet and key recovery flows are reviewed.
- Legal, tax, compliance, and consumer-risk reviews are complete.
- Security review and incident response plans are complete.
- Treasury, supply, reserve, and emission policies are approved.
- User-facing language clearly separates points, testnet tokens, and mainnet coins.

## Naming

- Service brand: PLAI
- Chain display name: PLAI Chain
- Canonical native asset: PLAIS Coin
- Canonical symbol: PLAIS
- Development name retained in history: AISFOR-CHAIN

Earlier Tokenomics v0.1 materials used PLAI/PLAI Coin as provisional names for
the six-decimal simulation ledger. The canonical Besu QBFT network uses PLAIS
Coin/PLAIS with 18 decimals. Configuration, genesis, Explorer, wallet, and
disclosure materials must not use conflicting identities at the same time.

## Supply Candidate And Ledger Separation

- Canonical genesis supply: 10,000,000,000 PLAIS
- Canonical decimals: 18
- Current public circulating supply: 0
- Maximum TGE unlock after separate launch approval: 800,000,000 PLAIS (8%)
- Ecosystem/user rewards: 32%
- Node/storage/validator rewards: 20%
- Foundation treasury: 15%
- Core team/contributors: 12%
- Ecosystem partners/grants: 8%
- Market/liquidity infrastructure: 6%
- Community launch/eligibility: 5%
- Security/user-protection reserve: 2%
- Private-sale allocation: 0%

The legacy plais Point ledger retains 6 decimals for data compatibility. It is a
simulation ledger, not part of canonical circulating supply, and conversion is
disabled. The candidate unlock schedule, circulation definition, wallet
segregation, reporting, and change controls are defined in
`docs/TOKEN_DISTRIBUTION_POLICY.md`. The schedule remains inactive until legal,
tax, custody, audited vesting, disclosure, and public-launch gates are approved.

## Point and Testnet Conversion Policy

Internal PLAI Point and testnet PLAI are evidence of activity and technical rehearsal. They are not a guaranteed future claim.

Allowed language:

- "Activity may be considered in future eligibility review."
- "Testnet balances are resettable and non-monetary."
- "Mainnet conversion policy is not yet approved."

Forbidden language:

- "1 point equals 1 coin."
- "Testnet PLAI will become mainnet PLAI."
- "Rewards are guaranteed."
- "This has investment value."
- "This will be listed."

If a future conversion or eligibility program is proposed, it must define:

- Snapshot date
- Eligible activity types
- Excluded abuse patterns
- Review and appeal process
- Conversion or grant ratio, if any
- Maximum claim cap
- Geographic and legal restrictions
- Expiration period

## Reward Policy

PoSS remains the candidate reward model: Proof of Service & Storage.

Mainnet reward policy must separate:

- Service usage contribution
- Storage and node contribution
- Content and emoticon creation
- Commerce activity
- Ecosystem and moderation contribution
- Validator operation

Mainnet rewards must include:

- Daily cap
- User cap
- Category cap
- Suspicious activity review
- Refund and cancellation exclusion
- Self-trading review
- Fake storage and fake commerce detection
- Delayed settlement
- Operator review record

## Validator and Node Policy

Mainnet validator/node policy is not yet approved.

Before approval, the policy must define:

- Node registration rules
- Minimum uptime
- Storage proof requirements
- Challenge/response verification
- Reward calculation
- Penalty or slashing rules
- Exit and cooldown period
- Hardware and bandwidth expectations
- Privacy and data custody rules

Node participation on current AISFOR sync-client or testnet does not automatically grant validator status on mainnet.

## Wallet and Transfer Policy

Current wallet features are for testnet and simulation only.

Mainnet wallet approval requires:

- Private key handling review
- PIN and recovery flow review
- Backup and restore testing
- Fraud and phishing warnings
- Withdrawal policy
- Transfer fee policy
- Address format finalization
- Explorer traceability
- User support process

External withdrawals and exchange deposits remain disabled until explicitly approved.

## Temporary TRX Collateral Gate

Before PLAIS Coin can be considered for native node collateral, TRX may be used as a temporary
node-participant collateral asset.

Policy currently enforced in code:

- Sync-client installation alone only makes a device a node candidate.
- General user activity rewards do not require TRX collateral.
- Node participant rewards require confirmed TRX collateral.
- The current collateral rate is 100 TRX per 1 TB of provided node capacity.
- The admin dashboard can update the TRX-per-TB rate and the base capacity threshold without code changes.
- Online, storage capacity, chunk stored, chunk verified, and restore contribution rewards are blocked until collateral is active.
- Offline node penalty is also blocked for non-collateralized nodes, because they are not active participants yet.
- If the collateral status check fails, node participant rewards fail closed and are not paid.

## Commerce Policy

Shopping, seller settlement, and emoticon sales can be tested with points and testnet tokens.

Mainnet commerce use requires:

- Refund handling
- Chargeback handling
- Tax and accounting review
- Buyer protection policy
- Seller abuse review
- Settlement delay policy
- Price volatility handling
- Consumer disclosure text

No real-money commerce settlement in PLAIS Coin is approved by this draft.

## Public Activation Gates

Public transfer and exchange-integration approval can proceed only after:

1. Testnet runs without critical ledger inconsistency.
2. Reward sources are stable across AISFOR, AISTALK, AISGROUP, and AISMALL.
3. Explorer can trace wallet, reward, audit, review, block, and proof records.
4. Admin dashboards expose readiness and rollback controls.
5. Abuse review queue is manageable.
6. Backup and restore procedures are tested.
7. Security review is complete.
8. Legal/compliance review is complete.
9. Token allocation and emission schedule are approved.
10. User-facing terms and risk disclosures are approved.

Until all gates pass and explicit approval is recorded, the canonical network remains technically live but public transfer access and circulating-supply activation remain locked.

## Current Decision

Current policy decision:

- Canonical QBFT network operation: allowed
- Technical mainnet preconditions: 11/11 passed
- Internal PLAI Point: allowed
- Reward simulation ledger: allowed
- Controlled testnet token rehearsal: allowed
- Public mainnet coin issuance: not approved
- Exchange listing: not approved
- External wallet withdrawal: not approved
- Mainnet point conversion: not approved

## Canonical EVM Mainnet Implementation

The canonical EVM-compatible PLAIS network is active and producing QBFT blocks.

- Chain id: `20260718`
- Client and consensus: Besu `26.6.1` with QBFT
- Topology: four validators on four independently attested hosts and one non-validator RPC node
- RPC binding: localhost only
- Native asset: PLAIS Coin (`PLAIS`), 18 decimals
- Wallet keys: secp256k1 with standard EVM addresses
- Key vault: AES-256-GCM with scrypt, user PIN, and a separate server vault secret
- External transfers: locked by configuration
- Existing point and mock-wallet balances: not migrated

The four validator identities run on four independently attested hosts. Validator
keys remain in audited encrypted envelopes, operator custody remains offline,
and RPC remains loopback-only. Public RPC, external deposits, withdrawals,
point conversion, circulating-supply activation, and exchange integration remain
locked until the public activation gates in this document are approved.
