KiraKIRA
Open Kira
Docs/start-here/

Kira documentation

Kira is a multi-chain workspace for managing wallets, preparing launches, coordinating bundle entries, trading live markets, and understanding the result from one interface.

Kira
FIGOne workspace from wallet preparation to post-launch trading.

What Kira covers

Kira connects the parts of a launch that are usually split across scripts, spreadsheets, explorers, RPC dashboards, and trading terminals. You can organize wallets, fund them publicly or through supported private routes, configure a project, choose a launch sequence, monitor the result, and act on managed positions without changing tools.

Wallets→

Create, import, organize, distribute, consolidate, claim, and inspect managed wallets.

Private funding→

Move value through supported private routes, bridges, and destination wallets.

Projects→

Configure token metadata, dev position, bundle allocation, execution, and launch readiness.

Launch modes→

Choose when creation, dev actions, bundle entries, and market checks happen.

Charts & trading→

Read live market activity, trade multiple wallets, and control dev positions.

PNL→

Review project results, wallet totals, daily history, and shareable cards.

The documentation follows those major workflows. Small actions such as copying an address or renaming a folder are explained inside the relevant workflow instead of becoming separate navigation pages.

Supported chains

Kira keeps the overall workflow consistent while adapting transaction construction, native units, confirmations, launchpads, and chain-specific actions to each network.

SolanaNative unit: SOL
Pump.funStonkFunAnsem

SWQoS/TPU-oriented execution, live account data, WSOL-aware trading, and Solana-specific lock support where available.

Robinhood ChainNative unit: ETH
PonsPoolsFlapVirtuals

Sequencer-oriented execution with EVM wallets, pool-specific quoting, live chart ingestion, and creator actions where supported.

BNB ChainNative unit: BNB
Four.memeFlap

EVM account model with BNB gas, chain-specific launch payloads, trading, funding, and PNL support.

Chain context matters
Always confirm the active chain before selecting wallets or executing an action. Wallet groups, balances, launchpads, native amounts, and transaction links are chain-specific.

The normal workflow

  1. Prepare wallets. Create or import wallets, organize them into folders, and confirm native balances.
  2. Fund the intended set. Use public distribution for visible transfers or a supported private route when source correlation matters.
  3. Create a project. Enter token identity, choose a launchpad, and select a launch sequence.
  4. Configure the dev position. Select the dev wallet and set the buy, supply target, burn, or chain-specific options.
  5. Build the bundle. Choose wallets, target total supply, and review Kira's correlated allocation.
  6. Launch from readiness. The Launch page shows what is resolved, what is missing, and the expected execution order.
  7. Monitor and trade. Open the chart, inspect the live tape, track managed holdings, and use the trading controls.
  8. Review PNL. Project and calendar views summarize bought, sold, holding value, and realized/unrealized results.

Read this before executing

Kira can prepare and submit irreversible on-chain transactions. A green readiness state means the configured checks passed; it is not a guarantee of market outcome, price, inclusion order, provider availability, or profit. Review the active chain, selected wallets, amounts, launchpad, and execution mode before confirming.

The Security page explains wallet handling, visible versus private routes, confirmations, operational limits, and the information Kira deliberately does not expose in public documentation.