Wave Hi
From Wave Wiki — the open reference for the Wave OS ecosystem.
1. About
Wave Hi is a decentralized messaging and social platform built as a lightweight Svelte web app, embedded into Wave OS via iframe. It features Channels (community chat), Feed (social posts), Mail (email via BMail44 bridge using oswave.cloud domain), and Beam (file transfer via RaptorQ fountain codes over Theta Edge nodes). Designed as the communication layer for the Wave OS ecosystem.
2. Tech Stack
Wave Hi Tech Stack (Rebuilt August 2026). Frontend: Base44 native app (React + Tailwind), published at wave-hi.base44.app. Mobile-first responsive design with bottom nav.
Backend: Base44 managed backend with entity storage (ChatMessage, Conversation, WaveHiProfile, WaveBeamTransfer, TFuelSettlement, EmailEvent). Row-level security enforced.
Theta EdgeCloud Relay: WebSocket relay deployed as a Docker container on Theta EdgeCloud vm_c1 (us-central-1). Live 24/7 at wss://wavehirelay-q2p072jsfg6r2t24iebj3ttynfpy.tec-s1.onthetaedgecloud.com. Handles real-time message delivery for Channels. Cost: $0.05/hr. Replaces the old Railway relay.
File Storage: Pinata IPFS pinning service for decentralized, content-addressed storage. Files get real IPFS CIDs, retrievable via any IPFS gateway globally. Backend function wavebeamEdgeStore handles upload/retrieve/status via Pinata API.
TFUEL Settlement: tfuelSettlement backend function handles on-chain micropayments for spam prevention. Uses eth-rpc-api.thetatoken.org/rpc as primary endpoint. Fee schedule: chat_public 0.001 TFUEL, chat_dm 0.002 TFUEL, mail_dm 0.005 TFUEL, media_small 0.005 TFUEL, media_large 0.01 TFUEL. Fee split: 70% relay operator, 20% Theta treasury, 10% channel creator. Settles via ServicePaymentTx on Theta Mainnet.
Identity: Theta wallet generated client-side (private key never leaves browser). Wallet address linked to @handle via WaveHiProfile entity. Handles sync between Wave OS and Wave Hi via shared wave_os_email field. Handle changes have 30-day cooldown with 50-credit bypass fee.
Email: wavehi.io domain. BMail44 bridge for traditional email integration.
3. Install
Wave Hi is now a standalone Base44 app published at wave-hi.base44.app. It is also embedded as an iframe in Wave OS — navigate to app.oswave.io and open Wave Hi from the navigation. Quick start: go to wave-hi.base44.app, log in with Google, MetaMask, or email, and claim your @handle. Need detailed setup instructions? See our Setup Wave Hi guide for step-by-step login, handle registration, and wallet linking instructions. Difficulty: Easy (pre-installed in Wave OS, no separate setup needed for basic use).
4. Pricing & Credits
Free tier uses Wave credits for AI features and message sending. Beam file transfers may use Wave credits for Theta Edge storage. No TFUEL costs for basic messaging. Power tier: connect Theta wallet for decentralized features. No separate subscription required.
5. Known Limitations & Roadmap
Pinata API rate limits apply to free tier. IPFS gateway retrieval speed depends on gateway and network conditions. Files are pinned via Pinata but not replicated to additional IPFS nodes automatically.
6. Privacy & Data
Messages stored in Wave OS database via Conversation and ChatMessage entities. User profile data (avatar, bio, theta_wallet) stored in User entity. Mail bridge uses oswave.cloud domain for email routing — email content stored in BMail44 system. Files are stored on IPFS via Pinata pinning service. Content hashes (CIDs) are stored in WaveBeamTransfer entity records. IPFS content is publicly accessible by CID — no access control on stored files. Encryption is handled client-side before upload.
7. Published by
Published by xBuildy. GitHub repo: xBuildyTeam/wave-hi. Created date: [PLACEHOLDER]. Version: [PLACEHOLDER].