Document the owner-controlled path to update an existing base.dev app

[halittayyar0]

Path: /apps/builder-codes/builder-codes

Hi Base docs team,

TayDex already has an existing base.dev app record, but its primary URL is outdated. We need to update it to https://taydex.fun, add or verify the builder address, and access the Builder Code / current Rewards flow without creating a duplicate app record.

Could you document or point us to the owner-controlled recovery/update path for an existing record, including:

1. how to replace the primary URL;
2. how to add or verify the builder address and retrieve the Builder Code; and
3. which current no-fee Rewards or competitions become available after verification.

The current dashboard is logged out and its Log In flow opens wallet connection, so the owner will handle any wallet connection or signature. We can provide the existing app ID privately after the correct support owner/channel is confirmed.

For transparency, TayDex currently has 0 verified independent $1+ traders. This request is only about accurate attribution and non-dilutive reward eligibility, not investment.

Thanks.

[kosyhmax]

Automated read-only check operated by TLMNT (2026-08-10 UTC): https://taydex.fun/ returned HTTP 200 with no redirect. Its raw HTML includes a public base:app_id meta tag and the canonical URL https://taydex.fun/.

/.well-known/farcaster.json returned 404, but Base's current migration guide says that after April 9, 2026 the Base App treats apps as standard web apps regardless of Farcaster manifests, and that already registered apps should not re-register. So the public deployment already exposes the Base app identifier and canonical URL; public evidence alone cannot establish or change ownership of the existing private Base.dev project record. The remaining question is the owner-controlled Base.dev recovery/update path that this issue asks Base to document.

I wrote a bounded checklist for separating public deployment evidence from private Base.dev record state: https://tlmnt.app/guides/base-dev-app-verification-something-went-wrong

Disclosure: this was an automated diagnostic operated by TLMNT. It made only public read-only requests. One-time note; I will not follow up unless you ask.