What is SonoSig?
SonoSig is a browser-based tool for adding wallet-signed proof data to audio files and checking that proof later. It is built for creators who need lightweight provenance before audio spreads across platforms.
FAQ
Frequently asked questions.
Practical answers about SonoSig proofs, audio encoding, wallet signatures, verification, and creator workflows.
What is SIWE?
SIWE means Sign-In with Ethereum. In SonoSig, your wallet signs a structured message that says this wallet is making a claim about this audio. The signature can be verified without trusting SonoSig as the only source of truth.
Why encode a SIWE proof into audio?
Audio often leaves the platform where it was uploaded. Embedded proof helps preserve attribution and verification context when a file is downloaded, renamed, sent in a chat, or uploaded somewhere else.
Is the proof tied to the actual audio?
Yes. SonoSig does not only encode that a wallet signed something. It encodes that wallet X signed this specific audio fingerprint, at this time, for this purpose, with this nonce. During verification, the browser recomputes the fingerprint from the watermarked WAV or AIFF and rejects files where the audio no longer matches the signed claim.
What fields are embedded in the watermark?
The payload includes protocol, ENS name, wallet, audio_fingerprint, audio_hash, manifest, issued_at, nonce, chain_id, signature_type, and signature. SonoSig also keeps local compatibility fields for verification display.
Which song metadata can SonoSig import?
When available, SonoSig reads common ID3, MP4/iTunes, and WAV INFO tags for title, artist, album, album artist, composer, genre, release date, year, track, disc, ISRC, BPM, key, publisher, copyright, and comments. These fields stay editable before signing.
How can I use AI to make music?
Use an AI music generator to sketch ideas, create loops, draft lyrics, build background beds, or explore alternate versions. Export the audio, review the tool's license terms, add clear metadata, then encode the finished file with SonoSig so the generated track carries a wallet-signed proof.
Why is WAV or AIFF preferred for verification?
WAV and AIFF keep the embedded payload in PCM samples, so SonoSig can recompute the signed audio hash directly. M4A and OGG are available for convenient local export and sharing, but lossy encoding can change sample data, so exact audio-hash verification is strongest with WAV and AIFF.
Does this replace copyright registration?
No. SonoSig creates a technical proof of a signed claim. It can help with provenance and evidence, but it does not replace legal registration, contracts, split sheets, or professional legal advice.
Can a watermark be removed?
Any audio watermark has limits. SonoSig is designed to be harder to lose than ordinary metadata, but aggressive editing, destructive conversion, or targeted removal can damage verification.
Is my audio uploaded?
No. Decoding, encoding, preview, export, and verification happen locally in your browser.
What should I encode?
Use SonoSig for meaningful versions: demos you share, release candidates, stems, client previews, licensed assets, or important revisions. Avoid encoding every tiny scratch file.
What makes a proof stronger?
Use a wallet people can recognize, include clear song metadata, keep the original exported proof file, and record related context such as collaborators, dates, agreements, or release links.