1. Register the proof with PacStac
SonoSig submits the wallet-signed audio proof to PacStac so the claim can be indexed by wallet, claim ID, audio hash, fingerprint, and related metadata.
ENS
SonoSig uses ENS as a creator-controlled public pointer, not as the full song registry. The ENS record points agents to a PacStac wallet collection where multiple audio claims can be discovered.
ENS text key
com.sonosigENS text value
pacstac:wallet:0x1234567890abcdef1234567890abcdef12345678This collection pointer avoids the one-record-per-song problem. ENS stores the stable wallet collection location, while PacStac stores and indexes all SonoSig claims registered by that wallet.
SonoSig submits the wallet-signed audio proof to PacStac so the claim can be indexed by wallet, claim ID, audio hash, fingerprint, and related metadata.
SonoSig writes the creator's ENS text record key com.sonosig with a compact PacStac collection pointer.
Verifiers and agents read the ENS text record, discover the creator's PacStac wallet collection, then query PacStac for the latest registered SonoSig claims.
A verifier resolves the creator ENS name, reads com.sonosig, confirms the value starts with pacstac:wallet:, and uses the wallet address as the PacStac collection key. PacStac remains the source for claim lists, status, and per-song metadata.
ENS transactions may show as complete in the wallet before the app refreshes the receipt. SonoSig records submitted transactions locally, refreshes pending statuses on the Transactions page, and treats submitted ENS updates as visible pending actions until confirmation is observed.
Earlier SonoSig workflows may have written a single latest claim pointer into com.sonosig. New implementations should prefer the PacStac wallet collection pointer so one ENS name can represent every song registered by the creator wallet.