1. Platform & Investor Experience
Scope of the authenticated Aerion platform: account entry, wallet connection, the ARN activation flow, ten dashboard views, and a public transparency page. It is delivered as a separate application on its own subdomain; the existing launch site is not replaced.
1.1 Entry & accounts
The platform is delivered as a separate authenticated application. The existing launch site is not replaced and remains the public front door.
- 1The application is served from its own subdomain. The recommended address is app.aerion.network. Aerion sets the final address.
- 2Account creation by email, role-based permissions, defined account states, and a basic user-editable profile.
- 3Every account carries an investor access status. Existing waitlist entries are migrated into platform accounts.
- 4The build connects to existing Aerion assets: the live launch site, investor-access lead capture, the Investor Hub and Technical Whitepaper references, and the published roadmap covering public sale, dashboard go-live, liquidity readiness and POMP activation.
- 5Current links continue to resolve. Roadmap milestones are modelled as states the dashboard displays.
1.2 Wallet connection
One wallet address per Aerion account.
- 1Base-compatible wallet connection. The connected address is bound to the Aerion account and used for allocations, receipts and portfolio data.
- 2Wallet balances are displayed in the dashboard. Transactions report pending, confirmed or failed status.
- 3Locked, vested and claimable states carry a plain-language definition wherever they appear.
- 4Every on-chain reference links to the corresponding record on the Base block explorer.
1.3 Token activation
Approved users request or buy ARN through a four-step flow with an admin review step. No allocation is issued automatically.
| Ref | Step | Action |
|---|---|---|
| A-01 | Purchase intent | The user submits an ARN allocation request with the destination wallet address. |
| A-02 | Admin review | Aerion reviews the request in the admin console against the KYC status field on the account. |
| A-03 | Allocation record | An approved request is stored as an allocation record with amount, campaign bonus and terms. |
| A-04 | Receipt | A receipt is issued in the dashboard. Purchase and allocation records are exportable. |
- Bonus display
- The campaign bonus in effect — 2–3% or the figure Aerion approves — is displayed against the requested amount.
- Reference price
- Where a DEX or CEX reference price exists, it is displayed alongside the request.
- Inventory availability
- Availability is read from treasury or dashboard inventory. Requests cannot exceed available inventory.
- Wallet address
- The destination wallet address is collected as part of the request and stored against the allocation record.
- KYC status
- A status field by default. If Aerion selects a provider, that provider is integrated instead. Scenarios and pricing impact are set out at §6.4.
- Exportable records
- Purchase and allocation history export for finance, reporting and reconciliation.
- Disclaimers
- Risk and utility disclaimers appear inside the activation flow. No return is promised in any surface of the flow.
- Risk acceptance
- The user must acknowledge the risk disclosure before submitting a request. The acknowledgement is stored against the allocation record.
- Legal pages & consent
- Terms and privacy notice routes plus a cookie consent prompt are included in the build. Aerion supplies the wording; Polenist builds the pages and the consent flow.
Boundary — Confirmed by Aerion
Legal structure, payment processor, KYC provider and approval of the sale itself are decided and confirmed by Aerion and its advisors. This build delivers the interface, data model, admin workflow and integrations on top of those decisions.
1.4 Dashboard views
Ten authenticated views are included in this build.
| Ref | View | Contents |
|---|---|---|
| V-01 | Overview | Account and wallet state, headline balances, active campaigns, and the user's pending action. |
| V-02 | Token Activation | Where a purchase or allocation stands, which bonuses applied, issued receipts, and the destination wallet. |
| V-03 | Portfolio | ARN allocations held, locked amounts, vesting schedule, and currently claimable balance. |
| V-04 | Pools | Mining pools and the planned AI and HPC pools: utilisation, VNIM scenarios, absorption coverage. |
| V-05 | POMP | Reserve position, activated inventory, and availability tied to measured performance. |
| V-06 | Service Credits | Credit balance, standing reservations, consumption history, and future compute and service access. |
| V-07 | Access & Bonds | Dashboard tier, access locks in effect, verifier and provider bonds, and participation record. |
| V-08 | AI Operator | Site status, energy-to-compute spread, dispatch logic per decision, and the assistant's written explanation of that decision. |
| V-09 | Exchange Readiness | Token and network details, listing progress, liquidity links, and transfer notices. |
| V-10 | Support & Documents | Approved documents, FAQs, stated risk boundaries, and the support request route. |
1.5 Public transparency page
One page, viewable without an account, built from references Aerion has approved.
- 1Approved on-chain reserve references.
- 2Current vesting and lock status.
- 3Treasury or dashboard inventory references.
- 4POMP reserve status.
- 5BaseScan links for each figure shown.
Exclusion — Not in this build
Real-time assurance tooling and third-party attestations are excluded and quoted separately as a follow-up module. The v1 page publishes approved references and links to the chain. It does not certify them.