Wallet-native access
A signed challenge can prove eligibility without creating another password or exposing a seed phrase.
Roadmap · development only
DevelopmentA utility path for Ophelia.
This page describes product ideas under consideration. No token, mint, sale, or launch is presented on this site today.
This is a product roadmap, not financial advice or an investment offer.
Why this network
Solana is being evaluated as infrastructure, not a slogan.
The question is whether wallet-based access can make Ophelia easier to use and sustain. If it cannot improve the product, it should not ship.
Low-cost usage records
Small, auditable service-credit events may be practical without turning every chat message into an on-chain transaction.
Portable eligibility
A user could prove access across Telegram and web while each channel keeps the same private account boundary.
Possible utility
Access could be part of the conversation.
A token-gated access model may let holders chat with Ophelia. That is a product-access idea, not a promise of availability, ownership value, or a current way to participate.
Verify access
Connect a wallet and sign a one-time challenge; Ophelia verifies eligibility and never asks for a seed phrase.
Open a private session
An approved holder enters a private Telegram or web session—not a shared memory pool. Each session needs its own identity, history, limits, and deletion controls.
Meter real usage
Token-linked service credits become a measured usage allowance; model-provider credentials stay server-side and are never handed to a user or bot client.
Sustainable operation
Usage and creator rewards may help fund the work.
Model and voice
Future usage could help cover the model and voice costs behind a responsive assistant.
Hosting and operations
Creator rewards and paid usage, if a future launch venue provides them, could help cover model, voice, hosting, and operations.
Product first
Any utility design must serve a real product experience before it earns a broader role.
Phased roadmap
No launch before the product and controls work.
Dates stay deliberately unset until the previous phase has evidence. “Planned” means design work, not a promise to launch.
Research
Define access, cost accounting, wallet privacy, abuse limits, and a sustainable user experience.
Private prototype
Test wallet challenges, isolated identities, Telegram and web access, quotas, revocation, and deletion.
Security and legal review
Review contracts, custody boundaries, disclosures, tax treatment, moderation, treasury controls, and incident response.
Launch decision
Proceed only if the utility is useful, costs are sustainable, controls pass review, and public terms are ready.
Security boundary
The wallet proves access. It does not become the assistant.
No seed phrases
Ophelia would request a standard signed challenge only. She would never ask for recovery words or a private key.
No wallet custody
The access service would verify public wallet state without taking control of user assets.
Private memories stay separate
Wallet eligibility would not create a shared memory pool. Identity, history, deletion, and rate limits remain isolated per user.
Provider keys stay private
Model, voice, and messaging credentials remain server-side behind quotas and abuse controls.
What remains open
Important decisions are not settled.
The roadmap will stay explicit about these decisions rather than fill the gaps with a launch narrative.
Access rule
Balance threshold, holding period, supported wallets, renewal checks, revocation, and whether access uses holding, spending, or another proof.
Usage accounting
How service credits map to model cost, rate changes, daily caps, exhaustion, unused balances, refunds, and provider fallback.
Treasury and rewards
How creator rewards and usage proceeds are recorded, separated, disclosed, and applied to operating costs.
Safety and legal
Moderation, rate limits, abuse response, wallet privacy, tax treatment, jurisdiction, consumer disclosures, security review, and launch approval.
Straight answers
Before anyone connects a wallet.
Has an Ophelia token launched?
No. There is no token, public token identifier, presale, or public access sale presented by this site.
Would Ophelia ever need my seed phrase?
No. A legitimate access check needs only a wallet signature. Never provide recovery words or a private key.
Would every message be written on-chain?
No. Conversations and memories must remain private. The proposed chain role is eligibility and bounded accounting, not publishing chat history.
Is access guaranteed for token holders?
No access rule has been approved. Eligibility, usage limits, supported channels, pricing, and revocation remain development decisions.
Are creator rewards guaranteed to fund Ophelia?
No. Rewards depend on a future venue and activity. Any operating allocation would need transparent records and public disclosures.