Document the owner-controlled path to update an existing base.dev app
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 40/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- documentation
Research direction
Start at /apps/builder-codes/builder-codes and review the existing documentation around app ownership and updates. Confirm the owner-controlled path for changing the primary URL, verifying the builder address, retrieving the Builder Code, and accessing current Rewards or competitions without creating a duplicate record. Done means these steps and the appropriate support owner or channel are documented clearly.
Written by the indexing model from the issue text.
Description
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:
- how to replace the primary URL;
- how to add or verify the builder address and retrieve the Builder Code; and
- 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.
- Dominant language
- JavaScript
- Stars
- 337
- Forks
- 798
- Avg merge
- 13h 7m
- Merged PRs (30d)
- 57
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from base/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mksglu/context-mode#1200 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
neondatabase/website#5944 ·
-
module: core
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
bigbluebutton/bigbluebutton#25849 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jaegertracing/jaeger-ui#4506 ·