LAOD.inUPLOAD
Connect Spotify
LAOD DOCUMENTATION v1.0

Build culture.
Understand the rails.

Complete product and technical documentation for music attention markets on Base.

Base networkDoppler markets3 audio sources29 topics

What is LAOD?

Music attention markets on Base.

LAOD turns songs into on-chain attention markets. Fans can discover and play music, collect or trade songcoins, curate releases, and interact with artists. Artists can publish releases, manage a public profile, receive attributed fees, and claim eligible imported-song identities.

A songcoin represents a market associated with a song. It does not grant copyright, royalties, equity in an artist, or a guaranteed return. Imported metadata is attribution, not proof that an artist created or endorsed the coin.

  • Base mainnet
  • Doppler and Uniswap v4 market infrastructure
  • Spotify, SoundCloud, and native/IPFS playback
  • Fan, Artist, and Curator navigation modes
Back to top ↑

Quick start

Discover, listen, collect, or launch.

Browse Music Coins, search by song or artist, and press play on a card. Native audio, Spotify, and SoundCloud use different playback paths but share the persistent player experience.

To transact, sign in or connect a compatible wallet on Base. Review every quote, slippage setting, network fee, and contract interaction before signing.

  • Browse at /coins
  • Open an artist at /artists
  • Create or import at /coins/create
  • Open Music Copilot with Cmd/Ctrl+K
Back to top ↑

Discovery and catalog

Search the indexed song catalog.

The home page and /coins are the primary discovery surfaces. Search matches indexed song names, tickers, artists, descriptions, and compact metadata. Filters cover genre, source, ownership, and Spotify visibility.

The catalog is an indexed list of known addresses, not an exhaustive chain explorer. Results and counts become reliable after loading completes. A newly created browser session can also recover recent launches from local storage.

Back to top ↑

Playback

Native, Spotify, and SoundCloud audio.

Uploaded tracks use the native HTML audio/IPFS path. Spotify imports use Spotify Web Playback when connected. SoundCloud imports use its player and best-effort preview resolution.

The persistent mini-player survives navigation. Native and Spotify playback are coordinated to avoid competing sources. The visualizer can be toggled from the interface or with V; theme can be toggled with B.

  • Spotify full playback requires OAuth and Premium
  • Browser autoplay rules still apply
  • Some imported tracks have no preview
  • Cross-origin audio may play without supporting visualization
Back to top ↑

Music coins

The central song and market page.

A coin page combines song metadata, artist attribution, playback, contract links, market data, ratings, curator actions, collectibles, artist claim tools, sharing, and holder community access.

A coin can exist before it has traded. LAOD suppresses placeholder prices and market caps until observed market activity exists.

Back to top ↑

Trading

Buy and sell songcoins on Base.

Trading supports configured ETH, LAOD, and USDC routes. Doppler markets can use WETH or a supported tokenized stock as numeraire. The route shown depends on the coin, selected payment token, wallet capabilities, and available liquidity.

Attention market cap is derived from the Doppler curve and is not DexScreener FDV. Market history is swap-derived. Sales require a supported market and sufficient liquidity.

Back to top ↑

Wallets and Base

Authentication, balances, ramps, and transfers.

LAOD is configured for Base. It supports Privy embedded wallets and compatible external wallets through Wagmi and OnchainKit. Spotify OAuth is separate from wallet authentication.

Balance discovery focuses on indexed song tokens; it is not a general portfolio scanner. Coinbase ramp availability, KYC, geography, payment methods, and fees are controlled by Coinbase.

Back to top ↑

Auto Support

Listening-triggered micro-buys.

Auto Support can trigger a configured micro-buy after a listening threshold, subject to a daily limit. Pro Mode uses Base Account sub-accounts and spend permissions when configured.

Treat this as automated crypto trading, not passive income. Wallet prompts, paymaster behavior, and eligible playback sources can vary by wallet and deployment configuration.

Back to top ↑

Curator Club

Curation, governance, playlists, and perks.

Curators can vote for a daily King, hide or rate songs, use proposals when the governance contract is configured, and build wallet-keyed playlists. Shared playlist snapshots can be published and imported.

Draft playlists live in the browser. Published snapshots update only when the curator explicitly updates the share. Membership and governance availability depend on configured contracts and payment infrastructure.

Back to top ↑

Collectibles and shop

Limited song editions and unlocks.

The shop distinguishes available, stealth, coming-soon, and sold-out collectibles. Edition eligibility can depend on songcoin holdings or Curator Club membership.

Physical holder drops shown in product copy are future benefits unless a specific item presents an active fulfillment flow.

Back to top ↑

Messages and holder lounges

XMTP conversations and gated communities.

/messages opens the configured XMTP song-agent conversation. Coin holder lounges require an authenticated wallet and positive token balance for that coin.

XMTP browser storage may be exclusive to one LAOD tab. Group admission can require an existing member. App-level mute policy may not affect messages sent from another XMTP client.

Back to top ↑

Music Copilot

Voice, image, and playlist-driven actions.

The persistent copilot accepts conversational prompts and Spotify or SoundCloud playlist links. It resolves up to 50 tracks, marks duplicates and already-coined songs, and presents a selectable review. Cmd/Ctrl+K opens it.

Push-to-talk sends explicitly recorded audio to the configured transcription endpoint. Camera/image attachment is a progressive input; full visual song recognition depends on the configured model pipeline.

Back to top ↑

Create or import a songcoin

Streaming import, native upload, or existing coin.

/coins/create supports Spotify/SoundCloud import, native audio and cover upload, and existing on-chain coin onboarding. Launch metadata includes name, ticker, description, genre, artist attribution, source details, and optional supported stock pairing.

Native upload requires a wallet. Streaming import can use backend launch and pending artist attribution. A first buy is a separate action; the launch can succeed even when seeding or the first buy fails.

  • Ticker: 1–11 letters, numbers, _ or -
  • Music rights are not transferred by metadata import
  • Duplicate platform IDs are checked
  • Audio, cover, and metadata may be pinned to IPFS
Back to top ↑

Artist dashboard and profile

Releases, links, handles, and public identity.

The artist dashboard finds indexed releases attributed to the active wallet and summarizes catalog market data and holders. Displayed market cap is not a withdrawable earnings balance.

Public profiles support wallet and vanity-handle URLs, featured releases, external links, and a tag-style landing view. Only indexed releases attributed to the wallet can be featured.

Back to top ↑

Artist claims and escrow

Claim imported-song attribution and fees.

Streaming imports may begin with pending artist attribution. Spotify and SoundCloud verification flows resolve a platform artist identity and a wallet verification signal before registration or escrow transfer.

Metadata credit is not proof of ownership. Legacy Zora and current Doppler assets follow different claim paths. Generic /claim creator-reward withdrawal is separate from imported-song ownership and fee escrow.

Back to top ↑

System architecture

Next.js, providers, APIs, protocol libraries, and contracts.

LAOD is a Next.js 14 App Router application. Routes and UI live under app/, protocol and domain logic under lib/, Solidity and Hardhat under contracts/, tests under tests/, and operational scripts under scripts/.

The provider tree composes theme, brand state, UI mode, native audio, Spotify, playback coordination, Privy, OnchainKit, Wagmi, React Query, trade currency, LAOD purchase modal, queue, and copilot state.

app/          Pages, components, APIs, contexts and hooks
lib/          Doppler, escrow, stock and protocol logic
contracts/    Solidity, deployments and Hardhat tests
data/         Seed and fallback data (not durable production storage)
scripts/      Operations, indexing, deployment helpers
tests/        Vitest protocol/domain tests
Back to top ↑

Doppler launch lifecycle

Scheduled multicurve launch and registration.

A launch validates metadata and artist routing, builds an eight-band scheduled multicurve auction, deploys through Doppler, attempts a seed purchase, then records token, pool, artist, protocol, and source metadata.

The initial supply is one billion tokens. WETH is the default numeraire; an allowlisted Coinbase tokenized stock can replace it. Unknown and legacy assets require careful protocol detection.

LAOD scheduled multicurve

Eight liquidity bands · 100% of configured curve shares

Market cap →
1$1–$100
8%6 positions
2$100–$500
10%6 positions
3$500–$1K
12%8 positions
4$1K–$5K
14%10 positions
5$5K–$20K
16%12 positions
6$20K–$100K
18%10 positions
7$100K–$500K
13%8 positions
8$500K–MAX
9%1 position
Each band allocates a share of sale liquidity across its market-cap range. The final band is an uncapped tail. This visual shows launch configuration, not a forecast of price or market cap.
Back to top ↑

Fees and escrow

Beneficiaries, collection, LAOD conversion, and artist routing.

Doppler takes a mandatory 5% protocol share. The remaining 95% is split by the configured app artist/treasury ratio. With a nominal 50/50 app split, effective allocation is approximately 47.5% artist and 47.5% treasury.

The fee pipeline collects pool fees, determines artist share, converts eligible WETH to LAOD, credits per-coin escrow proof, records a ledger entry, and can forward to a dedicated ArtistWallet.

Back to top ↑

Smart contracts

Curation, ratings, editions, registry, escrow, and queues.

Contracts include LAODEscrow, ArtistWallet, SongCastCuration, SongCastRatings, SongCastEdition, SongCastArtistRegistry, CuratorClubProposals, SongCastPoints, UserMusicQueue, AppCreditRegistry, and legacy escrow/governance contracts.

LAODEscrow separates admin, creditor, and forwarder roles and accounts per coin proof. Production administration should preserve role separation and use a multisig where specified.

Back to top ↑

API families

The main server interfaces.

App Router APIs cover launches, Doppler market data, trades, Spotify/SoundCloud, catalog indexes, AI copilot, curation, ratings, editions, artist profiles, Curator Club, shop, holder chat, notifications, and ramps.

Mutation authorization and anti-abuse are route-specific. Do not assume every POST endpoint shares a global auth or rate-limit layer.

/api/songs/*              Launch and fee operations
/api/doppler/*            Registry and market data
/api/trade/*              Route quotes
/api/spotify|soundcloud/* Media metadata and claims
/api/coins/*              Catalog data and batch review
/api/copilot/*            Chat and transcription
/api/curation|ratings/*   Signed community actions
/api/holder-chat/*        Token-gated XMTP policy
Back to top ↑

Data and persistence

Redis, JSON fallbacks, browser state, and chain state.

Redis/KV backs catalog indexes, platform mappings, shared playlists, waitlists, and holder-chat policy when configured. JSON files provide seeds and local fallbacks. Browser storage holds recent launches, preferences, draft playlists, gateway cache, and some XMTP state.

Ordinary Vercel filesystems are ephemeral. Whole-file read/modify/write is vulnerable to concurrency races. In-memory idempotency and jobs reset across instances and deployments.

Back to top ↑

Media integrations

Spotify, SoundCloud, IPFS, and Pinata.

Spotify uses client credentials for public metadata and OAuth/Web Playback for user playback. SoundCloud uses API v2 resolve and track endpoints. Playlist resolution is capped at 50 tracks.

IPFS metadata and media use server proxies, Pinata, cached gateway resolution, and fallback URLs. Keep Pinata credentials server-only.

Back to top ↑

AI and XMTP

Bankr gateway, transcription, playlist intent, and messaging.

The copilot uses a configurable OpenAI-compatible Bankr endpoint. Playlist URL parsing is deterministic and works without an LLM. The model is constrained from claiming unconfirmed execution or describing coins as equity or guaranteed investments.

XMTP powers agent messages and holder groups. The legacy XMTP x402 signer is placeholder logic and is not production payment authorization. Browser XMTP local keys stored in localStorage inherit XSS and extension risk.

Back to top ↑

Environment variables

Configuration groups and secret boundaries.

Create private deployment variables for chain/RPC, Privy, Doppler deployer, treasury and escrow, Spotify/SoundCloud, Pinata, Bankr/transcription, Redis/KV, XMTP, contracts, relayers, and cron operations.

Only values intentionally required by browser code may use NEXT_PUBLIC_. Private keys, API secrets, relayer keys, Redis credentials, and Pinata secrets must remain server-only.

BANKR_LLM_BASE_URL=
BANKR_LLM_API_KEY=
BANKR_LLM_MODEL=deepseek-v4
TRANSCRIPTION_BASE_URL=
TRANSCRIPTION_API_KEY=
TRANSCRIPTION_MODEL=whisper-1
ENABLE_LIVE_BATCH_LAUNCH=false
Back to top ↑

Deployment and operations

Builds, cron, agents, and protocol tasks.

The Vercel deployment uses a frozen pnpm install, Next build, and a six-hour Doppler-fee cron. Production cron requires CRON_SECRET. The standalone XMTP agent starts with pnpm agent:start.

Live Doppler integration and execution tests can contact Base or submit real transactions when explicit flags are enabled. Review environment and wallet funding before running them.

pnpm dev
pnpm build
pnpm test:doppler
pnpm budget
pnpm agent:start
pnpm test:doppler:mainnet
Back to top ↑

Security checklist

Known trust boundaries and launch blockers.

Protect deployer, relayer, escrow, XMTP, and Pinata credentials. Add consistent authentication, authorization, request-size limits, and rate limiting to mutation and upload routes. Replace runtime JSON and in-memory jobs with durable storage.

Use global security headers appropriate to the deployment, restrict remote image hosts, audit intentional framing routes, monitor cron failures, and preserve escrow role separation. Treat all LLM tool calls as untrusted suggestions validated by deterministic server policy.

  • No public secrets
  • No autonomous model spending
  • Durable idempotency for launches
  • Transactional fee accounting
  • CSP, HSTS, Referrer and Permissions policies
  • Contract tests for escrow and privileged paths
Back to top ↑

Testing

Current suites and required release checks.

Vitest covers Doppler launches, fees, fee ledger, coin proofs, escrow routing, artist resolution, sanitization, stocks, and SoundCloud helpers. Hardhat covers selected editions, registry, proposals, and staking contracts.

Before release run TypeScript, focused unit tests, full protocol tests with RPC access, production build, and browser smoke tests for desktop/mobile discovery, playback, launch review, trading, claims, and wallet states.

Back to top ↑

Glossary

Common LAOD terms.

Attention market: a market associated with cultural attention around a song. Songcoin: the fungible on-chain token for that market. Numeraire: the asset paired with the songcoin. ArtistWallet: a dedicated contract used for artist routing. Coin proof: the escrow key derived from token address and artist identity.

Indexed catalog: LAOD’s known-address dataset, not every compatible token on Base. Pending claim: attribution or fees held until artist verification. Curator hide: a community signal that can affect discovery, not deletion from the blockchain.

Back to top ↑
LAOD

Music attention markets on Base.

Music coins are volatile cryptoassets. They are not copyright, royalties, artist equity, or guaranteed investments.