You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[fix] Reconcile token lists with the persisted verified registry #1706
Description:
GET /tokens reads a static in-memory list while GET /tokens/:address and GraphQL read TokenRegistry. Persisted verified assets never appear in the list, and individual lookup metadata can disagree with the list.
Acceptance Criteria:
Serve list, detail and GraphQL metadata from a consistent verified registry, retaining documented caching behavior.
Insert or update a verified database asset and assert that the list and detail endpoints agree on its metadata and verification status.
Notes:
Source trace: token.routes.ts imports listVerifiedTokens from lib/token-metadata, while getToken and GraphQL read Prisma TokenRegistry.
Audited commit: 649b6976a100fd964ce191428eef1faeb50aaa39. Closest prior issues reviewed: #1323, #1515. This report concerns the specific failure or uncovered test paths described above, rather than repeating the original feature request.
@Ottones has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
I’ve looked over the issue and know how to handle the fix. I have successfully handled similar tasks and I am available to start working on it right away.
Congratulations, @ojuotimi932! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @ojuotimi932: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
😎 @ojuotimi932: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
Activity
Ottones commentedon Oct 21, 2026
@Ottones has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ottones to this issue.
KingJiggy commentedon Oct 21, 2026
@KingJiggy has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @KingJiggy to this issue.
Clararosey67 commentedon Oct 21, 2026
@Clararosey67 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Clararosey67 to this issue.
Ayfataan commentedon Oct 21, 2026
@Ayfataan has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ayfataan to this issue.
Mukhtar003 commentedon Oct 22, 2026
@Mukhtar003 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Mukhtar003 to this issue.
ojuotimi932 commentedon Oct 22, 2026
@ojuotimi932 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @ojuotimi932 to this issue.
olalekan22-tech commentedon Oct 22, 2026
@olalekan22-tech has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @olalekan22-tech to this issue.
drips-wave commentedon Oct 22, 2026
Congratulations, @ojuotimi932! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @ojuotimi932: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
drips-wave commentedon Oct 22, 2026
This issue has been completed by @ojuotimi932 as part of the Stellar Wave Program's 10th Wave 🥳
😎 @ojuotimi932: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.