A token you can hear.

01. Overview

Soundhood pairs audio tokens with permanent recordings. Listeners can recover the stored bytes, inspect their onchain fingerprints, and review each token's market and fee rules.

The design has two markets. Public audio tokens use Soundhood's own factory, bonding curves, router, and Uniswap V4 hook. Official SOUNDH uses the existing Pons V2 factory and trades under Pons's rules. Soundhood's catalogue and contract records distinguish those origins.

Soundhood is independently operated and is not affiliated with Robinhood. Using Pons and Uniswap infrastructure does not imply their endorsement.

02. Audio inscriptions

For tokens created by Soundhood's own factory, audio and optional image bytes are stored in immutable contract bytecode. Each token records the locations, media types, and keccak256 fingerprints. The inscription cannot be replaced after launch.

Own launches support up to 16,384 audio bytes and 6,144 optional image bytes. Audio formats are WAV, MP3, and OGG. The current interface prepares larger recordings as short mono WAV excerpts of up to 1.95 seconds. Creators preview the final media before signing.

Official SOUNDH uses a separate audio registry. Its original Pons deployer may create an immutable registry associating media bytes and hashes with the token address. This does not add audio storage or an audio getter to the Pons token itself. The official registry address must be published alongside the token address, because more than one registry could be created.

A token purchase does not transfer copyright, a recording licence, or commercial usage rights. Creators must have permission to publish their audio and artwork.

03. Launching a token

On Soundhood, a creator chooses a name, symbol, sound, and optional cover, then reviews the creation fee, optional first purchase, gas, and price tolerance. The own router creates a token and its curve, with an optional purchase in the same transaction.

Each own launch starts with one billion tokens and no further minting. The supply initially belongs to its bonding curve. Creators receive an opening allocation only through an explicit purchase. The first own launch may use any valid name; official SOUNDH is issued separately on Pons.

The curve prices buys and sells from its tracked reserves. Virtual ETH is a pricing parameter, with no deposited ETH behind it. Real purchases add ETH, and sales remove ETH, after fees. Own launches permanently disable creator taxes and opening taxes.

04. Liquidity migration

Own launches retain the Pons V2 curve and migration math: a 1.68 ETH virtual reserve and a nominal graduation target of 4.2 ETH in trading reserves, excluding accrued fees. Graduation occurs when the curve's sale allocation is exhausted. Integer rounding and trading history determine the exact final amounts.

A purchase exceeding the remaining sale allocation is partially filled and unspent ETH is refunded. Its price tolerance applies to the actual spend; the received quantity can shrink with the fill.

Own graduation first settles the curve reserves, then creates the Uniswap V4 pool and mints a full-range position into a permanent locker. The Soundhood router attempts completion after the final purchase. Failed completion remains a visible, retryable pending phase.

The own liquidity-position NFT and additional locked supply have no withdrawal path. Locked tokens remain in total supply and are distinct from burned tokens. Graduation requires market demand and is not guaranteed. Official SOUNDH's graduation is managed by Pons.

05. The official SOUNDH token

Official SOUNDH is planned for the canonical Pons V2 factory on Robinhood Chain. The dedicated deployment wallet will be its original deployer, and the treasury will receive its creator fees. Planned launch settings are creator tax zero, Pons’s optional buyback and five-year vesting disabled, and no initial purchase.

Its verified address will be published with the live release. The Soundhood platform vault will verify and permanently bind the external token’s Pons record, original deployer, treasury, name, symbol, and native ETH pool terms. A matching name or ticker alone does not establish authenticity.

The platform buyback budget is reserved for this external SOUNDH market. Holding SOUNDH does not grant ownership of Soundhood, access to treasury funds, or a guaranteed income stream. The separately published immutable audio registry identifies the official recording once deployed.

06. Fees and token economics

Own-platform audio tokens: the trading fee is 1%, divided equally between creator and platform. The curve charges fees on the ETH side. After graduation, the own V4 hook collects the fee and the pool's separate core fee is zero. Fees collected in a launch token require conversion before they become distributable ETH.

These percentages divide earned trading fees. Of the platform's half, 70% accumulates in ETH for a future SOUNDH buyback mechanism and 30% is payable only to the immutable operations treasury. For example, 100 units of own-platform trading fees allocate 50 to the creator, 35 to the future buyback budget, and 15 to operations.

A separate creation fee, when configured, is platform revenue and follows that platform 70/30 allocation. Network gas is paid to the network. Fee budgets remain separate from curve and pool trading reserves.

Official SOUNDH on Pons: its creator fees are a separate revenue stream paid to the treasury through Pons's escrow. They do not enter Soundhood's own 70/30 allocation. Under the Pons policy used by this design, normal base fees are 1%, split 30% to Pons and 70% to the creator, with optional per-token vesting disabled. Pons controls its launch-window taxation and protocol terms; Soundhood's zero opening tax does not apply to that external market.

07. Future buyback activation

Buybacks will be disabled at startup. No production price oracle is supplied, deployed, proposed, or activated with this release. The 70% budget can accumulate, but the vault cannot execute purchases while its oracle is unset. The authority has no withdrawal path for that budget.

A suitable oracle for the exact external SOUNDH pool requires a separate design review. Occasional spot-price samples are not equivalent to a cumulative record of every swap. A test oracle used in local simulations is not suitable for production.

• Public proposal: the fixed deployment authority may propose an oracle address and runtime code hash, subject to a three-day delay.
• Separate activation: after the delay, the authority must submit another transaction. SOUNDH must have graduated, and the oracle's code and pool identity are checked again. Waiting alone cannot activate it.
• One-time binding: a pending proposal can be cancelled; a new proposal restarts the delay. An activated oracle cannot be replaced.
• Retained execution limits: any later execution remains subject to price-history warmup, freshness, price-deviation and slippage checks, purchase-size limits, aggregate spending limits, and cooldowns.
• Fixed accounting and destinations: purchases can spend only the allocated budget on the bound SOUNDH token. The retained purchase-and-burn path checks the supply reduction in the same transaction.

No buyback execution calendar is announced. Any future purchase requires a submitted transaction and all applicable conditions to hold. Accumulation does not promise a purchase date or eventual activation.

Oracle selection remains an administrative trust assumption. A pinned code hash does not establish price correctness or rule out changing behaviour through proxies or external dependencies. The public delay provides notice, not a security audit. Burns do not guarantee demand, liquidity, or a higher price.

08. Administration and transparency

Soundhood retains owner controls over opening public launches, launcher permissions, creation fees, and the launch forwarder. Creator-fee recipients can transfer their recipient role; the owner retains a delayed override. Certain delayed recovery actions remain available for incomplete migrations. Compatible hook administration also remains, subject to the factory's pinned fee terms and per-launch snapshots.

The deployment authority alone can propose and activate the future oracle. The operations treasury is immutable; anyone may submit its claim transaction, but the payment can go only to that treasury. No administrator can withdraw the reserved buyback budget, change an own token's media, mint additional supply, or withdraw its completed locked liquidity.

Pons's own administration governs the external SOUNDH market. Its permissions must be reviewed separately from Soundhood's own contracts. The operational manifest will publish both sets of addresses and explicitly identify the official audio registry.

Verified source, deployment wiring, owner roles, fee recipients, and oracle status will be published before activation. Onchain balances and completed transactions will provide evidence of revenue allocation and any later burns.

09. Release status and limitations

This interface has no configured, verified hybrid deployment. It remains a pre-launch preview and does not present simulated balances, local fork transactions, or burns as live activity.

Before public launches open, the real Pons SOUNDH record, own contracts, wiring, immutable media, fee recipients, retained powers, and disabled buyback state must be verified. Market data and trading must be connected to the correct contract family. A later oracle activation requires its own review, explicit transaction, and a reviewed interface release.

Local tests support only the scenarios they cover and do not establish that every exploit has been excluded. Audio tokens are speculative assets: prices may fall to zero, liquidity may be limited, graduation may never occur, and transactions can fail or be irreversible. This document makes no promise of returns.