Octria is a product. Octra is the network.
Octria is an independent, community-built product suite made of two connected interfaces: Octria Wallet and Octria Launchpad. The wallet manages accounts, balances and approvals. The launchpad lets people discover, create and trade token markets without handing custody of their account to the website.
Octra is the underlying blockchain network. It provides OCT, programs, OCS-01 tokens, public and encrypted balance primitives, and the execution environment on which Octria is being built. Octria is not the Octra network, is not an official Octra client, and is not affiliated with Octra Labs.
Accounts, approvals, OCT, encrypted OCT and token portfolio.
Creation, discovery, bonding-curve trading and market data.
What Octria Launchpad is
Octria Launchpad is a catalog-first, non-custodial market interface for launching fixed-supply OCS-01 tokens on Octra. A creator supplies a name, ticker, image, description and optional first buy; the launchpad prepares the required program calls and asks Octria Wallet to approve them.
The website is not an exchange operator and does not hold user funds. Public markets are programs on Octra. Quotes are derived from their reserves, and successful transactions settle on the network. The product layer focuses on understandable approvals, discovery, charts, portfolio views and risk facts.
The current launch protocol
A launch is six explicit on-chain actions: deploy the token, deploy the market, fund inventory, activate the market, publish it to the registry and execute the creator's first buy. Octria presents every approval separately.
Confirmed transaction hashes and public contract addresses are saved on the device so an interrupted launch can resume without repeating completed steps.
- Deploy tokenCreate the fixed-supply OCS-01 program.
- Deploy marketCreate its OCT bonding-curve program.
- Fund inventoryMove the curve allocation into the market.
- Activate marketEnable quotes and market execution.
- Publish marketRegister the canonical token–market pair.
- Initial buyExecute the optional creator position.
The multi-step flow is intentionally transparent during mainnet alpha. A future permissionless factory should make creation simpler and more atomic, but only after child deployment and failure recovery are reliable.
Market model
Each token trades against its own OCT bonding curve. Contract reserves set the live quote, demand moves the price and slippage protection defines the minimum acceptable output. There is no off-chain order book or hidden matching engine in the launchpad.
The curve and its reserves determine the quote, not an Octria server.
Wallet-approved program calls settle against the market contract.
AMM graduation, migration and routing remain future protocol work.
The long-term trading loop is curve → canonical liquidity → DEX routing. Graduation must atomically preserve reserves and prevent an operator from replacing or silently removing canonical liquidity.
Market truth and data architecture
Identity, supply, reserves, counters and live quotes come from Octra programs. The registry provides canonical token–market relationships. The optional read-only indexer reconstructs public history for search, activity and candles; it does not hold keys, sign transactions or decide settlement.
Local storage is used only for recoverable interface state such as a partially completed launch. It must never become the source of truth for whether a market exists or how much liquidity it contains.
- Direct program reads for live reserves, prices and market status.
- Canonical registry for public discovery and address verification.
- Read-only indexer for durable trades, OHLCV, search and analytics.
- Realtime delivery is planned for confirmations and market updates.
Trust and security model
The website never receives a private key, mnemonic, PIN or raw signature. Octria grants account visibility per exact website origin and opens its own approval window for every deployment and contract call.
Non-custodial does not mean risk-free. A user still trusts the displayed program address, wallet simulation, compiled program code, network RPC and the correctness of unaudited contracts. Token creators can also publish misleading metadata or concentrate supply.
Roadmap without invented dates
This roadmap describes dependencies and direction, not delivery promises. Stages can change order when Octra's runtime, encrypted operations or audit findings require it. Features move forward only when the layer beneath them is measurable and recoverable.
Transparent launch and curve trading
OCS-01 launches, registry discovery, direct program reads, charts, portfolio, explicit wallet approvals and a read-only public indexer.
Make public markets dependable
Permissionless factory, canonical event schema, archive backfill, realtime confirmations, OHLCV, holder distribution, creator history, metadata validation and factual risk panels.
Complete the DEX loop
Canonical AMM, router, automatic graduation and migration, locked liquidity rules, improved simulation, alerts, creator vesting and transparent fee attribution.
Octra-native private markets
Encrypted OCT settlement experiments, private trade intent, batch clearing, fair-start launches, private watchlists and token-gated sealed Circles.
Cross-chain execution
Quotes, routing and portfolio control across external networks through explicitly disclosed bridges, relayers or intent solvers.
Supporting work includes a documented read-only SDK, stronger mobile layouts, accessibility, creator updates, anti-spam controls and public incident communication. Social feeds, referrals and gamification are secondary to correct market data and safe settlement.
Encrypted OCT and private markets
Octra supports a public OCT balance and an encrypted balance. Moving OCT into encrypted form is not the same as executing a private trade: a market still needs rules for private intent, price limits, matching, proofs, settlement, refunds and reserve accounting.
Octria's proposed dark-pool direction is a private-market venue where encrypted OCT can be used to reduce pre-trade information leakage. The research target is to keep order amounts and limits private until a batch can settle at a fair clearing price, revealing only what execution requires.
Encrypted commitments enter a short window and settle together instead of exposing the first buyer to copy-trading.
A user privately expresses “buy or sell up to X within limit Y”; settlement reveals only the necessary result.
There is no release date. Shipping requires protocol support, deterministic proof generation, invariant and adversarial testing, protection against failed batch settlement, privacy analysis and an independent audit.
Cross-chain trading is a long-term direction
The product goal is to let an Octria user view positions, request a quote and manage trades on external networks from one interface. The implementation could use bridges, wrapped assets, relayers, intent solvers or chain-specific accounts. No architecture has been selected and there is no target date.
Cross-chain execution expands the trust surface far beyond Octra. Bridge compromise, relayer censorship, solver behavior, external-chain finality, liquidity fragmentation, fees, custody assumptions and recovery all have to be visible before a user signs.
- First: read-only multi-chain portfolio and quote research.
- Then: testnet intent routing with explicit execution paths.
- Before mainnet: bridge and solver threat models, audits and failure drills.
- Always: show the actual chain, route, fees, counterparties and trust assumptions.
This work is intended to improve user privacy and control, not to promise untraceable activity or disguise the origin and destination of funds.
Status, risks and official Octra resources
This is experimental mainnet-alpha software. Contracts are unaudited, AMM graduation is not enabled and public history depends on the available registry, receipts and optional indexer. Use only amounts you can afford to lose.
Octria Wallet and Octria Launchpad are independent community-built products. They are not developed, operated, sponsored, endorsed or audited by Octra, Octra Labs or the Octra core team. “Octra,” “OCT” and protocol references are used only to identify the network with which Octria interacts.