artist identity
Creator profiles anchor public artistic identity without making the website the source of truth.
artist-owned identity • transparent rights • native streaming economics
music without the black box.
420Hz is the music layer of 420 Integrated: artist profiles, releases, playback, discovery, rights, streaming settlements and royalty routing built around verifiable protocol state.
checking network status…
discover
one place for music, provenance & payouts.
Live catalog data will appear here after the public testnet deployment. Until then, this site stays intentionally fail-closed instead of presenting fixture data as real releases.
catalog & releases
Albums, releases, track ordering and presentation metadata project from canonical protocol history.
playback
Media manifests and storage sources resolve playback while preserving content-hash integrity.
rights & credits
Works, recordings, contributors and rights versions remain inspectable instead of hidden behind platform accounting.
streaming economics
Settlement epochs, allocation and STREAM royalty routing are explicit protocol surfaces.
rebuildable discovery
The public catalog is a non-authoritative projection that can be rebuilt from canonical event history.
artists
your work should know who made it.
420Hz is designed around creator profiles, works, recordings, contributor credits and explicit rights versions. Artist pages will surface those relationships directly rather than flattening them into opaque platform metadata.
live artist directory pending
HZ-AUDIT-7 public-testnet deployment is the gate for real catalog data.
streaming
play counts are not money until the accounting closes.
ORIGINALSTREAM v1 economics defined
REMIXSTREAM v1 economics defined
REBUILDABLEindexer projection
FAIL-CLOSEDpre-live environment
creator studio
publish when the chain is ready.
The creator studio will connect Wallet review, creator identity, work and recording registration, catalog publication, media manifests and STREAM economics against the verified deployment.
No transaction controls are enabled while the canonical testnet chain ID, deployment addresses and Registry bindings are unresolved.