Update secondary frontend surfaces #436
No reviewers
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:open_issues
agents
agent:security_audit
agent:verify
area
timecurve
arena
arena-v2
audit
block:feature_review
block:security
bug
contracts
design
devops
docs
documentation
enhancement
epic
feature
frontend
indexer
low priority
megaeth
operations
ops
performance
QA
qa checklist
referrals
removal
security
smart-contracts
tech-debt
testing
time-arena
timecurve
visual-qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
code/yieldomega!436
Loading…
Reference in a new issue
No description provided.
Delete branch "cursor/frontend-secondary-surfaces-0aa4"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Updates secondary frontend surfaces for GitLab #296 so
/referrals, third-party venues, 404, and fallback pages match the approved cyberminimalist platform UX.What changed:
/arena/{code}(legacy/timecurve/{code}remains redirect compatibility only).How this satisfies #296: the scoped referrals, venue, 404, and fallback surfaces now share the same dark tactical glass hierarchy, current product mechanics, compact copy, standardized
AddressInlinetreatment where present, and no visible stale TimeCurve/sale/PvE cross-sell framing.Related issues
Related to #296 (leave issue open for maintainer acceptance)
Design review notes
Primary user goals:
Primary decisions/actions surfaced:
/referrals: Register, copy/arena/{code}/?ref=links, track Guide CRED / Buyer CRED / Total CRED, and inspect guide leaderboard.Stale assumptions removed:
/arena/{code}.Layers touched
frontend/)Acceptance and verification checklist
/referrals,/kumbaya,/sir,/definitely-not-a-route;CI=1 npm run test:e2e -- --workers=5 e2e/referrals-surface.spec.ts e2e/navigation.spec.ts e2e/footer-site-links.spec.tsdocs/product/referrals.md;referrals-surface.spec.tsasserts 5 + 5 CRED and compact CRED copyreferrals-surface.spec.tsnegative visible-copy assertion; Rabby smoke rejectsTimeCurve path, sale-end/redemption/launchpad/PvE on touched routescd frontend && CI=1 npm run test:e2e -- --workers=5 e2e/referrals-surface.spec.ts e2e/navigation.spec.ts e2e/footer-site-links.spec.tscd frontend && npm run typecheckcd frontend && npm run lintcd frontend && npm testcd frontend && npm run buildbash scripts/check-doc-anchors.shxvfb-run -a node ...withlaunchRabbyContext: checked/referrals,/kumbaya,/sir,/definitely-not-a-route, and/referralsat 390x844Visual/design verification checklist for third parties
/referralsdesktop: CRED Network badge, compact hero, Register. Share. Track CRED., 1 CL8Y burn, One code, 5 + 5 CRED badges./referralsregister/share: configured registered wallet shows canonical/arena/{code}and?ref=share links; no visible TimeCurve path label./referralsleaderboard: rows use blockie + last-sixAddressInline; summary labels are compact (Codes, Referred buys, Guide CRED)./referralswallet panel: separates Guide CRED, Buyer CRED, Total CRED, and recorded buys./kumbayaand/sir: hero says Third-party venue. Verify off-site.; external CTA is primary when configured; Time Arena and AUDIT are visible recovery actions; snapshot labels external trust boundary.Accessibility and responsive notes
PageBadge, andStatusMessageprimitives are preserved.title/ ARIA-adjacent labels where possible; visible copy remains compact.AddressInlineblockie + last-six labels./referralspassed with no horizontal overflow.Licensing & compliance
Author checklist
Security review
Commit reviewed:
d8a43969c3fec2ff8aab9c51ed86ee2f91c926c4Scope: MR !436 — secondary frontend surfaces (
/referrals,/kumbaya,/sir, 404/fallback), docs, and E2E assertion updates (15 files, frontend + docs only).Outcome:
FINDINGS: 0medium+What was reviewed
ReferralRegisterSection.tsx): canonical path updated from/timecurve/{code}to/arena/{code}; query variant still usesencodeURIComponent. Displayed codes come from on-chainownerCode(normalized[a-z0-9]{3,16}) — not attacker-controlled at render time. Path capture still flows through existingnormalizeReferralCode/ reserved-slug checks.ThirdPartyDexPage.tsx): outbound URLs remain build-timeVITE_*env only; external anchor keepsrel="noopener noreferrer". New links are internal React RouterLinktargets (/arena,/arena/protocol).AddressInline/ formatted numerics (React text nodes, nodangerouslySetInnerHTML).NotFoundPage,UnderConstruction): copy/navigation only.Prior threads
No prior security-review notes on this MR; nothing to re-report.
Security review: no medium+ findings on this diff.
added 1 commit
f8382b0e- Handle unconfigured referral registry in e2eCompare with previous version
changed the description
mentioned in issue #296
Security review
Commit reviewed:
f8382b0e1fefd86c8e6a99556ea36a3770e27e1dScope: MR !436 — secondary frontend surfaces (
/referrals,/kumbaya,/sir, 404/fallback), docs, E2E assertions (15 files; frontend + docs only).Outcome:
FINDINGS: 0medium+Delta since prior review (
d8a43969)Only
frontend/e2e/referrals-surface.spec.tschanged: the register-section heading assertion now accepts Claim your guide code or Registry when the referral registry address is unset in CI. Test-only; no production code or auth/data-path changes.What was reviewed (full diff)
ReferralRegisterSection.tsx): canonical path is/arena/{code}(was/timecurve/{code}); query variant still usesencodeURIComponent. Displayed codes come from on-chainownerCode/ stored match ([a-z0-9]{3,16}) — not attacker-controlled at render time. Path capture still flows throughnormalizeReferralCodeandisReferralSlugReservedForRouting.ThirdPartyDexPage.tsx): outbound URLs remain build-timeVITE_*env only; external anchor keepsrel="noopener noreferrer". New recovery links are internal React RouterLinktargets (/arena,/arena/protocol).AddressInline/ formatted numerics (React text nodes; nodangerouslySetInnerHTMLin this package).NotFoundPage,UnderConstruction): copy/navigation only.Prior threads
Prior review on
d8a43969reported zero medium+ findings; nothing to re-report with fresh evidence.Security review: no medium+ findings on this diff.
mentioned in commit
ba83efef80mentioned in commit
3449bfa47c