Practical overview
When it fits
Use Aurora to explore and play music, maintain playlists, connect with artists or share tracks with local-first storage. Developers can use the repository instructions to start the app locally and optionally configure Pinata for IPFS persistence.
Who it is for
- Listeners who want to discover tracks, follow artists and organize playlists in a Web3 music app.
- Artists who want to upload audio and cover art, share posts and receive ETH tips.
- Developers interested in a TypeScript and React music-sharing application with local-first storage and optional IPFS integration.
Documented uses
- Browse engagement-ranked music and social feeds.
- Upload tracks and cover art, storing them locally or optionally through Pinata-backed IPFS.
- Create playlists and revisit liked songs.
- Follow artists and interact with posts through likes and comments.
- Send ETH tips to creators through MetaMask.
Requirements & limits
The repository is public and specifies an MIT license. Local development requires Node.js 18 or later; MetaMask is listed for wallet features.
- Storage is local-first: IPFS persistence through Pinata is an optional configuration.
- ETH tipping uses MetaMask and plain transfers; the repository says there is no smart contract for a music NFT.
- The player is documented with dual-deck crossfades, a 10-band equalizer and spectrum/waveform visualizations.
- Wallet identity is stored in localStorage and is not verified with a signature.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up Aurora locally
Install and start Aurora’s web app for local development.
Before you start
- Node.js 18 or later
- MetaMask extension for wallet features
Steps
Clone the Aurora repository and change into its directory.
Run npm install to install dependencies.
Optionally copy .env.example to .env.
Run npm run dev and open http://localhost:5173.
Expected outcome
The local development app starts with seeded demo artists, tracks and posts.
Guide limitations
- The MetaMask extension is needed for wallet features, not listed as a prerequisite for starting the app.
- The documented setup starts a development server; it does not describe a production deployment.
Configure optional IPFS upload storage
Enable Pinata-backed IPFS persistence for Aurora uploads.
Before you start
- A local Aurora setup
- Pinata JWT and gateway URL
Steps
Obtain Pinata keys from the Pinata dashboard.
Set VITE_ENABLE_PINATA=true in the project’s .env file.
Set VITE_PINATA_JWT and VITE_PINATA_GATEWAY in .env.
Expected outcome
Aurora is configured to use Pinata for optional IPFS persistence instead of relying only on browser-local storage.
Guide limitations
- IPFS/Pinata is optional; the app uses local storage by default.
- The instructions cover configuration, not verification of an upload.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- chxmq/Aurora · Official homepage title · retained in its source language

