Production metadata correction required
IssaDAO is correctly launched, indexed, and tradable on Pons, but its immutable token metadata was launched blank. The public Pons page therefore renders initials and No description yet. even though the creator has since supplied and signed the canonical metadata in Sinjoh.
This token must not be relaunched or replaced.
Exact launch identity
Canonical metadata
Confirmed live root cause
The deployed Pons client function readPonsV2TokenDetails multicalls the token's immutable logo() and description() getters and renders those values directly. Both getters return blank for this existing token. The deployed API exposes a creator-signed override only for social links:
PUT /api/pons-token/{token}/socials- signature action:
token-socials
- database table:
token_social_overrides
There is no corresponding metadata/description/logo route. OPTIONS confirms that /metadata, /description, /image, and /logo do not exist.
Minimal safe fix
Please extend the existing creator-signed override pattern rather than changing contracts:
- Add a creator-authorized metadata override keyed by
chain_id + token_address.
- Bind the signature to chain, token, creator wallet, description, logo URL, logo SHA-256, nonce, issued time, and expiry.
- Verify the signer is the launch creator/deployer for this exact token.
- Permit overrides only when the immutable onchain field is blank, so this cannot rewrite nonblank launch metadata.
- In
readPonsV2TokenDetails, use the verified override only for blank logo() or description(); preserve onchain values otherwise.
- Backfill only the IssaDAO row above, then verify the public page shows the exact description and logo while buy/sell remain unchanged.
No contract deployment, token relaunch, routing change, or trading change is needed.
Production metadata correction required
IssaDAO is correctly launched, indexed, and tradable on Pons, but its immutable token metadata was launched blank. The public Pons page therefore renders initials and
No description yet.even though the creator has since supplied and signed the canonical metadata in Sinjoh.This token must not be relaunched or replaced.
Exact launch identity
0x7A46AFFde334c0A5C923f4A6CC205add300750430xe4605138e185FBeE40ff6193A044aa0BE29092160xDe3553AA94B6de7586ECb9efFe206eA0fe01d53c0x8804c582f12511622fe2732bda7e8024bf9b8baa2f604b4dc552226fdd6fbef2Canonical metadata
The first investment DAO on Pons governed directly by token holders.e8f69dcfcd1c6bdf76811ce4392d2fc744046f7c38b6b844c0cdbc044a3bd0d81087603Confirmed live root cause
The deployed Pons client function
readPonsV2TokenDetailsmulticalls the token's immutablelogo()anddescription()getters and renders those values directly. Both getters return blank for this existing token. The deployed API exposes a creator-signed override only for social links:PUT /api/pons-token/{token}/socialstoken-socialstoken_social_overridesThere is no corresponding metadata/description/logo route.
OPTIONSconfirms that/metadata,/description,/image, and/logodo not exist.Minimal safe fix
Please extend the existing creator-signed override pattern rather than changing contracts:
chain_id + token_address.readPonsV2TokenDetails, use the verified override only for blanklogo()ordescription(); preserve onchain values otherwise.No contract deployment, token relaunch, routing change, or trading change is needed.