chAInletchAInlet FAOS
FAOS / DOCS

How FAOS works

A minimal agent interface for turning a human token request into a structured Flap deployment flow on BNB Chain.

Execution flow

FAOS separates intent from execution. The user describes a token, FAOS turns that request into structured launch parameters, renders a transaction preview, then hands final approval to the connected wallet.

USER INTENT → TOKEN CONFIG → PORTAL / VAULTPORTAL → PREVIEW → WALLET CONFIRMATION → BROADCAST → TOKENCREATED

Launch config

For a standard Flap launch, the protocol entrypoint is Portal. VaultPortal extends that path for tax tokens that attach vault behavior. FAOS keeps the human-facing layer simple while preserving the protocol boundary underneath.

$ chainlet launch --preview
name chAInlet
ticker CHAINLET
network BNB Chain
platform flap.sh
entrypoint Portal
✓ request ready for wallet review

Modules

The AI Store is the FAOS composition layer. Modules represent reusable launch behavior such as burn routing, buyback rules, fee splitting, liquidity guardrails, agent metadata and simulation. Installed modules are saved locally in this prototype and attached to the launch preview.

Wallet control

The Connect Wallet button uses an injected EVM wallet when available and requests BNB Smart Chain. This prototype stops at the confirmation boundary and does not fabricate a successful deployment.

FAOS prepares the request. Your wallet approves it. A token is only treated as live after a real on-chain transaction and deployed address exist.

Official Flap references

Token launcher quick startPortal / VaultPortal integration path ↗Deployed contract addressesBNB Portal: 0xe2cE…9De0 · VaultPortal: 0x9049…4C06 ↗TokenCreated indexingResolve creator, token address, name, symbol and metadata after launch ↗Registered vaultsOfficial vault factories and vaultData schemas ↗