Skip to content

Harden warning copy for stakeholder lockup contracts - #2

Merged
jim-counter merged 1 commit into
mainfrom
stakeholder-copy-updates
Mar 24, 2026
Merged

jim-counter merged 1 commit into
mainfrom
stakeholder-copy-updates

Conversation

@jim-counter

@jim-counter jim-counter commented Mar 24, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Replaced soft language ("may", "could") with definitive statements reflecting that Hedgey lockup contracts are non-revocable and have no admin role
  • Normalized references to cover both vesting and lockup contract types across the root page, verification form, and FAQ
  • No functional changes; copy updates only

Context

Stakeholder comms are going out this week directing recipients to the beneficiary portal. The portal copy needed to accurately reflect that lockup contracts cannot be modified after deployment, matching the language used in the outbound emails.

Files changed

  • src/pages/HomePage.tsx - welcome text, critical warning section
  • src/components/verification/verification-form.tsx - wallet requirements warning, attestation checkbox
  • src/components/verification/faq-section.tsx - unsupported wallets FAQ, change beneficiary FAQ

Test plan

  • Verify root page renders correctly with updated copy
  • Confirm attestation checkbox text reads accurately
  • Review FAQ accordion items for consistent language

Replace soft language ("may", "could") with definitive statements
reflecting that Hedgey lockup contracts are non-revocable and have
no admin role. Normalize references to cover both vesting and lockup
contract types across the root page, verification form, and FAQ.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@jim-counter
jim-counter merged commit 68a7196 into main Mar 24, 2026
2 checks passed
@jim-counter
jim-counter deleted the stakeholder-copy-updates branch June 13, 2026 12:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant