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
Mock activity timestamps are anchored at module load, so a long-running server shows the 'live' feed hours or days stale #707
recentActivity uses minutesAgo(n), computed once when mock-data.ts is first imported. On a long-lived Next.js server, the module stays loaded, so a day after deploy the homepage's "Live on the platform" feed reads "1 day ago" for every event. #201 replaced literals with this anchoring, which only works for short-lived processes.
Suggested fix
Compute the timestamps at render or request time (a function, not a constant), or stop presenting mock events as live.
@moon-code12 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
Hello Maintainers, I would like to express my interest in working on this issue. I have reviewed the issue description and understand the problem that needs to be addressed. My approach will be to investigate the existing codebase, identify the root cause, and implement a solution that follows the project's existing architecture and coding standards.
@Prudentdev-xyz has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
Hi maintainer,
I came across this issue and would love to work on it. I’m interested in contributing to real-world open-source projects and growing my engineering skills. I’ve also contributed to Web3 projects and open-source initiatives.
@Elioo12 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
Hello Maintainer, I have carefully reviewed the issue description and have a clear understanding of the expected outcome. I am interested in working on this task and confident in my ability to make a meaningful contribution. I would appreciate the opportunity to take it on. Thank you for your consideration.
Congratulations, @Prudentdev-xyz! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @Prudentdev-xyz: 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.
🏆 @Prudentdev-xyz: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (350 total points). Track your full progress on GrantFox.
👏 Great work, @Prudentdev-xyz! Keep contributing to MergeFi.
😎 @Prudentdev-xyz: 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
fix(mock): fictional sponsor names + render-time timestamps
CollinsKRO commentedon Oct 17, 2026
@CollinsKRO 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 @CollinsKRO to this issue.
harmondconsultant-png commentedon Oct 17, 2026
@harmondconsultant-png 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 @harmondconsultant-png to this issue.
tijanib141 commentedon Oct 17, 2026
@tijanib141 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 @tijanib141 to this issue.
Wittig18 commentedon Oct 17, 2026
@Wittig18 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 @Wittig18 to this issue.
moon-code12 commentedon Oct 17, 2026
@moon-code12 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 @moon-code12 to this issue.
Prudentdev-xyz commentedon Oct 17, 2026
@Prudentdev-xyz 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 @Prudentdev-xyz to this issue.
davidluxedesigns commentedon Oct 17, 2026
@davidluxedesigns 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 @davidluxedesigns to this issue.
chimdinduobidike23-norman commentedon Oct 17, 2026
@chimdinduobidike23-norman 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 @chimdinduobidike23-norman to this issue.
godwinedemodu commentedon Oct 17, 2026
@godwinedemodu 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 @godwinedemodu to this issue.
sim3onkiel commentedon Oct 17, 2026
@sim3onkiel 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 @sim3onkiel to this issue.
Elioo12 commentedon Oct 17, 2026
@Elioo12 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 @Elioo12 to this issue.
drips-wave commentedon Oct 17, 2026
Congratulations, @Prudentdev-xyz! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @Prudentdev-xyz: 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 🌊
grantfox-oss commentedon Oct 17, 2026
🎉 This issue has been marked as completed on GrantFox!
@Prudentdev-xyz's PR #807 was approved and merged by @chonilius.
🏆 @Prudentdev-xyz: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (350 total points). Track your full progress on GrantFox.
👏 Great work, @Prudentdev-xyz! Keep contributing to MergeFi.
drips-wave commentedon Oct 17, 2026
This issue has been completed by @Prudentdev-xyz as part of the Stellar Wave Program's 10th Wave 🥳
😎 @Prudentdev-xyz: 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.